Volume Permissions

[ryanmerolle]

Desired Behavior

Given docker volumes are written two by the docker user, volumes hosted to the underlying host for said container are created with the incorrect owner/permissions. If we figured out an elegant process for setting the uid/gid for the docker user in the environment variables, users would be able to setup rw volumes for the container and file permissions/ownership would match the user running the container. The use case would be for directories like media.

Contrast to Current Behavior

Right now the default id is uid=101 gid=0(root)

If you do not have root or sudoers access then you cannot edit or delete the files. If you move files into this volume from outside the container then in the container you would also have the opposite permission issues.

Changes Required

• Add an environment variable to map uid & gid.
• Add a process for updating the uid & gid to entrypoint.sh

Examples:

• https://github.com/arista-netdevops-community/docker-avd-base/blob/master/files/entrypoint.sh
• https://docs.linuxserver.io/images/docker-netbox#environment-variables-e

Discussion: Benefits and Drawbacks

Not too many drawbacks if the default uid/gid is set to be the same as it is currently. @tobiasge and I discussed this a few weeks ago.

[aryrz]

it's same issue for me. id=101 is default for "unit" user

[ryanmerolle]

another example

https://github.com/linuxserver/docker-baseimage-ubuntu/tree/xenial/root/etc/cont-init.d

Let me try to take a stab at this this week.

[mburgholte]

I am not sure if it is the same error. But after updating to the current version, it is no longer possible to upload pictures due to lack of permissions.