You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2020. It is now read-only.
Like most of the Docker official images, this image is currently configured to run as root. I'm opening this issue as a place to discuss what change should be made, if any. See this discussion in the context of the tomcat image for the sort of issues that can be anticipated for jetty.
I can see a few changes/enhancements being made to this image:
Add code to the Dockerfile to create a consistent jetty user to allow users to easily do USER jetty in a derived Dockerfile or -u jetty in their docker run command.
Document the use of JETTY_BASE for the jetty:9 image and give an example that uses --module setuid to drop privileges to the jetty user after starting as root.
The text was updated successfully, but these errors were encountered:
Like most of the Docker official images, this image is currently configured to run as
root
. I'm opening this issue as a place to discuss what change should be made, if any. See this discussion in the context of thetomcat
image for the sort of issues that can be anticipated forjetty
.I can see a few changes/enhancements being made to this image:
Dockerfile
to create a consistentjetty
user to allow users to easily doUSER jetty
in a derivedDockerfile
or-u jetty
in theirdocker run
command.JETTY_BASE
for thejetty:9
image and give an example that uses--module setuid
to drop privileges to thejetty
user after starting asroot
.The text was updated successfully, but these errors were encountered: