Closed ryannix123 closed 3 years ago
The boot script itself is running as root
as it is needed to set permissions.
Once it's done the container should not be using root
anymore.
So it seems your setup is detecting and restricting the usage of root
(which is a good thing, tbh), hence the container cannot start since it needs it to start.
I agree it's a good security practice not to run a container as root. OpenShift requires non-privileged users to run containers as non-root. Maybe I'll fork your Docker file and try to use Redhat's UBI8 instead.
The new image is 100% unprivileged, so I think I can close the issue!
Hello,
I went to deploy your image in OpenShift 3.11, however, I'm getting an error that the image is actually running as root. Any idea why that might be the case?
Image wonderfall/nextcloud runs as the root user which might not be permitted by your cluster administrator.