[2-EL10] Switch to running as the apache user - #92
Conversation
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
4 similar comments
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
In k3s, we were failing to start because our security policy disables running as root and that is the default user from the base container. When running in OpenShift, the pod is run with a random UID, groups root & random ID When running in k3s, the pod is now run as apache:apache The permissions need to allow writing to both directories in both cases.
|
Checked commit bdunne@ee26258 with ruby 3.3.10, rubocop 1.86.0, haml-lint 0.73.0, and yamllint 1.37.1 |
update-ca-trust/var/run/httpdis owned by root:apache, but the group has no permissions, in the restricted OpenShift SCC we need to allow the random UID to write to the directory.This fixes
Error: container has runAsNonRoot and image will run as rooton this container.Todo: