We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
su-exec is a third-party Alpine package i.e. not a part of GNU neither Apache project: https://github.com/ncopa/su-exec
Therefore, I thought maybe it can work just with su as well
https://github.com/bigdata-central/zookeeper-docker/blob/ubuntu/3.4.10/docker-entrypoint.sh
(thanks to DevOps SE https://devops.stackexchange.com/questions/2526/interference-of-docker-cmd-with-su-works-with-su-exec-but-not-with-su)
The text was updated successfully, but these errors were encountered:
The main motivation for not using su is that it spawns a child process
su
$ docker run -it --rm zookeeper su -c 'ps aux' PID USER TIME COMMAND 1 root 0:00 ash -c ps aux 8 root 0:00 ps aux
while su-exec does not
su-exec
$ docker run -it --rm zookeeper su-exec root ps aux PID USER TIME COMMAND 1 root 0:00 ps aux
And as it's said in https://github.com/tianon/gosu and https://github.com/ncopa/su-exec this might introduce some TTY and signal-forwarding issues.
Sorry, something went wrong.
No branches or pull requests
su-exec is a third-party Alpine package i.e. not a part of GNU neither Apache project:
https://github.com/ncopa/su-exec
Therefore, I thought maybe it can work just with su as well
https://github.com/bigdata-central/zookeeper-docker/blob/ubuntu/3.4.10/docker-entrypoint.sh
(thanks to DevOps SE https://devops.stackexchange.com/questions/2526/interference-of-docker-cmd-with-su-works-with-su-exec-but-not-with-su)
The text was updated successfully, but these errors were encountered: