permission change impossible on network drive about metube

[PikuZheng]

I have a similar operating environment. Every time I start metube, it reports lots of errors when modifying permissions, but it does not affect.

I think the key is whether the permissions are configured correctly when the host mounts /mnt/nas. You should first check whether it can be read and written normally, and then map it to the container.

If the host is a synology, I recommend setting the user id to the same as the synology admin's id.

[Neurofibromin]

The root user can write the folders just fine - in fact the .metube folder gets created. The problems start when metube tries to change the owner of the directory and lowers its privileges to user 1000:1000. I am using Truenas, but this is in fact not dependent on the nas at all - the owner setting is a limitation of the samba protocol itself.

I tried specifying in the compose file user: "0:0" but this changed nothing. I maintain: The ideal solution would be if metube just tried to create every downloaded file as root.

[PikuZheng]

As far as I know compose will change the folder permissions when creating the container. This may cause the folder permissions to not match what you expect.
I don't use compose, and I force read and write permissions when mounting the nas path. See #195 .

set UID: 0 and GID: 0 via environment variables, if you want to try.

[Neurofibromin]

I am not mounting the cifs share with docker: the cifs drive is already mounted by fstab, so I cannot change the permissions at mount (I'm not allowed to change fstab settings by company policy). I just tried user: "0:0", this does the same thing as UID: 0, GUID: 0. Compose will not change permissions, because fstab does the mounting. Samba does not support changing acls post-mount, pursuing that route is meaningless.

The solution would be if metube just tried to create every downloaded file as root. Is this possible?

[PikuZheng]

I just tried user: "0:0", this does the same thing as UID: 0, GUID: 0

i think the entrypoint.sh query the uid/gid in env only.

The solution would be if metube just tried to create every downloaded file as root. Is this possible?

yes UID: 0 and GID: 0 via env will do this but sometime root user is not 0:0 or disabled (ubuntu for example, root user name is not 'root' by default