You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the adduser command tends to create a user with an arbitrary UID, depending on the base image (https://github.com/obiba/docker-opal/blob/main/Dockerfile#L66). This makes it difficult to run opal in Kubernetes where explicitly setting the user id and group ip as part of the container's security context is necessary. I noticed this being a problem as both the docker.io/obiba/opal:5.0.2 and the docker.io/datashield/rock-base:6.3.1 tend to change the current UID between updates, causing updates to fail.
It would be great if the opal user's user and group id could be set to a fixed value and a USER directive be added to the Dockerfile. I'd be happy to create a PR if this seems reasonable!
The text was updated successfully, but these errors were encountered:
Currently, the
adduser
command tends to create a user with an arbitraryUID
, depending on the base image (https://github.com/obiba/docker-opal/blob/main/Dockerfile#L66). This makes it difficult to run opal in Kubernetes where explicitly setting the user id and group ip as part of the container's security context is necessary. I noticed this being a problem as both thedocker.io/obiba/opal:5.0.2
and thedocker.io/datashield/rock-base:6.3.1
tend to change the current UID between updates, causing updates to fail.It would be great if the
opal
user's user and group id could be set to a fixed value and aUSER
directive be added to the Dockerfile. I'd be happy to create a PR if this seems reasonable!The text was updated successfully, but these errors were encountered: