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
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
When using the girder_worker docker image, unable to run docker from within the worker container due to permission issue. Specifically the docker group does not appear to be created and worker user added to the group.
Docker executable and socket were mounted into the girder_worker container as previously described: #89
Error when trying to run docker from within the container:
worker@af4c874402be:/$ docker images
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/images/json: dial unix /var/run/docker.sock: connect: permission denied
The text was updated successfully, but these errors were encountered:
In the girder_worker docker, if the docker group has a different group id than the docker group of the host system, then there can be issues. In another project (https://github.com/DigitalSlideArchive/HistomicsTK), when creating a girder_worker docker, we explicitly change the uid and gid inside the girder_worker docker to match that of the host system, and the chown files to ensure that they have the right ownership.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the girder_worker docker image, unable to run docker from within the worker container due to permission issue. Specifically the docker group does not appear to be created and worker user added to the group.
Docker executable and socket were mounted into the girder_worker container as previously described: #89
Error when trying to run docker from within the container:
The text was updated successfully, but these errors were encountered: