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
One of the steps we do in entrypoint.sh is the adjustment of permissions for the user running inside the container. If DOCKER_UID is not set, we will use a default 1000.
Clearly, the user inside the container may not be the same instantiating the container from the host system. When that happens, the host system will complain ("permission denied") and the container will crash.
While the crash is undesirable, the mechanism in place is effectively to handle such situations -- i.e, when we need/want to set a likewise identity inside the container.
To work around the issue, pass the variable DOCKER_UID when instantiating the/a container. Suppose you are using the chbrandt/swift_deepsky -- a container that uses docker_commons:
$ docker run -it -e DOCKER_UID=$UID -v $PWD/work:/work chbrandt/swift_deepsky
The text was updated successfully, but these errors were encountered:
Issue found in a Fedora host.
One of the steps we do in
entrypoint.sh
is the adjustment of permissions for the user running inside the container. IfDOCKER_UID
is not set, we will use a default1000
.Clearly, the user inside the container may not be the same instantiating the container from the host system. When that happens, the host system will complain ("permission denied") and the container will crash.
While the crash is undesirable, the mechanism in place is effectively to handle such situations -- i.e, when we need/want to set a likewise identity inside the container.
To work around the issue, pass the variable
DOCKER_UID
when instantiating the/a container. Suppose you are using thechbrandt/swift_deepsky
-- a container that usesdocker_commons
:The text was updated successfully, but these errors were encountered: