Docker permission error using Slurm on HPC with Nextflow #4647
Unanswered
jdlamstein
asked this question in
Q&A
Replies: 1 comment
-
System admins do not allow docker to run on HPC systems because of security concerns. So the error is likely related to your local HPC policy rather than a bug. Instead, try switching to Singularity which does not have those Docker security concerns and is widely available on HPC systems. Here are some details for using Singularity with Nextflow (https://www.nextflow.io/docs/latest/singularity.html). I develop my docker images on my local iMac with Docker, push the container to the Docker hub, and then pull them with Nextflow/Singularty on the HPC. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
Similar issues include:
#2583
https://forums.docker.com/t/got-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket/113292
Expected behavior and actual behavior
I'm submitting a test workflow into the HPC with Nextflow. The test runs a hello world bash script. When I run this, I get a docker socket permission error:
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=nxf-vfPUNFEXBmP4OS8RLgRNOlTh": dial unix /var/run/docker.sock: connect: permission denied.
From what I can see, the
gid
of/var/run/docker.sock
is included inid --groups
.Steps to reproduce the problem
I run
nextflow run simpletest.nf
My simpletest.nf file is:
And my nextflow.config file is:
Program output
Below is the .nextflow.log
Environment
Additional context
Beta Was this translation helpful? Give feedback.
All reactions