When running this image in a Kubernetes Cluster and specifying runAsNonRoot in your security context, the pod is rejected as it does not specify a non-numeric USER in the spec (can't determine that the user is not root). Related PR: https://github.com/kubernetes/kubernetes/pull/56503
You can set runAsUser to a UID in your deployment spec to bypass this, but I thought it better to solve within the Dockerfile so other users won't run into this problem.
The USER could be changed to reference 2 (the UID for daemon user), but I thought this was a good point to create a specific user for the app (jira, UID 1000).
When running this image in a Kubernetes Cluster and specifying
runAsNonRoot
in your security context, the pod is rejected as it does not specify a non-numeric USER in the spec (can't determine that the user is not root). Related PR: https://github.com/kubernetes/kubernetes/pull/56503 You can setrunAsUser
to a UID in your deployment spec to bypass this, but I thought it better to solve within the Dockerfile so other users won't run into this problem.The
USER
could be changed to reference2
(the UID for daemon user), but I thought this was a good point to create a specific user for the app (jira, UID 1000).