1 of 3

Hands-on Sessions:�Troubleshooting

Simone Pagan Griso

for the Organizers

Workshop on the modeling of photon-induced processes

IPPP,

June 5th 2023

1

2 of 3

Can’t run docker

Symptoms: A common problem manifests when running docker:�/var/run/docker.sock: connect: permission denied.

Solution.

To solve this, make sure you add your user to the docker group:

sudo groupadd docker #in case this group does not exist yet

sudo usermod -aG docker $USER

and reboot your system (technically it’s enough to log out and log in again).

2

3 of 3

Permissions problems

Symptoms: files created within the container are visible outside the container but are not readable outside the container since they are from a different user (id).

Work-around:

  • I’ve produced a new version of the container, called:

spagan/yy-gen-playground:0.6-root

  • When running docker, do not specify the -u option, i.e. the full command will be:

docker run -it -v ${PWD}/yy-gen-playground:/work/yy-gen-playground -v ${PWD}/run:/work/run -- spagan/yy-gen-playground:0.6-root /bin/bash

If you still find files created inside the container can’t be read outside, when outside the container manually change file permissions to match your user with:

sudo chown -R yourusername:yourgroup folder

replacing yourusername and yourgroup to the user name and group used in your system outside the container.

known problem for several�Mac users

3