-
Notifications
You must be signed in to change notification settings - Fork 30
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
Allow usage with --user option #20
Comments
DarthGandalf
added a commit
that referenced
this issue
Feb 12, 2019
DarthGandalf
added a commit
to DarthGandalf/docker-official-images
that referenced
this issue
Feb 12, 2019
Thanks for the advice! |
DarthGandalf
added a commit
that referenced
this issue
Feb 12, 2019
DarthGandalf
added a commit
to DarthGandalf/docker-official-images
that referenced
this issue
Feb 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a feature request to have this container work with
--user [docker]
anduser: [docker-compose]
options.The way the current startup sequence is structured requires running
chown
to a container user with a predefinite UID and GID.Other images, however, (e.g. official postgres here for example), use lines like
chown -R "$(id -u)" "$PGDATA" 2>/dev/null || :
.Testing for
$(id -u) = 0
and changingznc:znc
to"$(id -u):$(id -g)"
in:znc-docker/slim/50-chown.sh
Line 4 in 207358a
as well as tweaking
su-exec
fromznc-docker/slim/99-launch.sh
Line 5 in 207358a
should be sufficient to allow arbitrary
--user
values and not break anything.The text was updated successfully, but these errors were encountered: