Replies: 1 comment
-
#3756 was filed to change this, contains some related discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We primarily utilize the opengrok container in its default configuration, with specific adjustments related to memory and thread settings: https://github.com/oracle/opengrok/blob/master/docker/README.md.
Presently, the container is deployed within one of our Kubernetes (k8s) clusters, where it doesn't have any issues with opengrok container running as root. However, a recent requirement has emerged, prompting the need to migrate the instance to a more secure k8s cluster. Unfortunately, this new cluster imposes restrictions against allowing the root user inside the container, resulting in the following error:
From a high-level perspective, creating a new user inside the container to meet opengrok's existing functionalities appears to be a complex task. However, we would appreciate your guidance in understanding the challenges involved if we decide to transition to a non-root user or if it's even possible with the current version of the opengrok container.
Beta Was this translation helpful? Give feedback.
All reactions