-
So since docker can port map any port to a container, I just need to map the port to one that the nginx user is allowed to access right? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
All the changes that have been made to this image have been made to ensure that the image will run in unprivileged environments. The easiest/safest way to achieve this in a container involves moving most of the files/processes/paths/etc that require privileged rights to the
Nope, unless you delete/remove the container or have some sort of temporary storage mount mapped to the
This would be the user ID/name under which NGINX is running (http://nginx.org/en/docs/ngx_core_module.html#user). It's deleted to comply with the OpenShift container standards (https://docs.openshift.com/container-platform/3.11/creating_images/guidelines.html#openshift-specific-guidelines).
That would be the NGINX process identifier. It tracks which process ID is tied to NGINX.
All |
Beta Was this translation helpful? Give feedback.
All the changes that have been made to this image have been made to ensure that the image will run in unprivileged environments. The easiest/safest way to achieve this in a container involves moving most of the files/processes/paths/etc that require privileged rights to the
/tmp
directory, since that directory is traditionally reserved for temporary files and most "restricted" environments allow r/w access to it. As long as you use the container the way it's meant to be used and do not run any additional software, running NGINX from that directory should not be an issue.Nope, unless you delete/remove the …