-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make UserID and Group ID of www-data match with host #1081
Comments
There's no need to create a user on the host. You can |
Why don't you add a UID & GID environment variable defaulting to 33 (default for www-data) to be able to specify the container's data UID & GID ? It would be way more convenient to integrate with other containers downloading files (like boypt/cloud-torrent for example) |
@J0WI depending on the host setup running the whole container as non-root can lead to other problems (e.g docker socket is not able to bind port 80 / other permission problems). I think it would be a nice feature (besides it seems to be a good practice in other docker projects) to especially set the uid/gid for the user who writes data. @rgarrigue but this was discussed in two other threads: and if you need this feature urgently i think you have to implement it.. 😄 |
fix: nextcloud#359, nextcloud#772, nextcloud#1081, nextcloud#1087, nextcloud#1278 Signed-off-by: J0WI <J0WI@users.noreply.github.com>
fix: nextcloud#359, nextcloud#772, nextcloud#1081, nextcloud#1087, nextcloud#1278 Signed-off-by: J0WI <J0WI@users.noreply.github.com>
closing due #1812 |
fix: nextcloud#359, nextcloud#772, nextcloud#1081, nextcloud#1087, nextcloud#1278 Signed-off-by: J0WI <J0WI@users.noreply.github.com> Signed-off-by: J0WI <J0WI@users.noreply.github.com>
I'm running Ubuntu 19.10 as my host OS.
I've ran into an issue where the user id and the group id of the
www-data
user/group are different on my host and in the nextcloud containers. This makes it difficult to move the data directory.In order to get this to work I had to do the following:
The text was updated successfully, but these errors were encountered: