Phil Ewels
04/01/2025, 9:51 AM.gitpod.yml config files from the pipeline template / core repos now? 🤔Maxime Garcia
04/01/2025, 9:51 AMMaxime Garcia
04/01/2025, 9:51 AMmashehu
04/01/2025, 9:53 AMMaxime Garcia
04/01/2025, 9:53 AMMahesh Binzer-Panchal
04/01/2025, 9:55 AMPhil Ewels
04/01/2025, 9:55 AMPhil Ewels
04/01/2025, 9:55 AMPhil Ewels
04/01/2025, 9:56 AMMahesh Binzer-Panchal
04/01/2025, 9:57 AMPhil Ewels
04/01/2025, 9:57 AMPhil Ewels
04/01/2025, 9:58 AM<http://mcr.microsoft.com/devcontainers/base:ubuntu|mcr.microsoft.com/devcontainers/base:ubuntu> and then uses Devcontainers features insteadPhil Ewels
04/01/2025, 9:58 AMMahesh Binzer-Panchal
04/01/2025, 9:59 AMPhil Ewels
04/01/2025, 10:00 AMMahesh Binzer-Panchal
04/01/2025, 10:00 AMPhil Ewels
04/01/2025, 10:00 AMPhil Ewels
04/01/2025, 10:01 AMPhil Ewels
04/01/2025, 10:02 AMPhil Ewels
04/01/2025, 10:03 AMJonathan Manning
04/01/2025, 10:07 AMFrancesco Lescai
04/04/2025, 3:37 PMPhil Ewels
04/04/2025, 7:38 PMPhil Ewels
04/04/2025, 7:38 PMFrancesco Lescai
04/04/2025, 8:58 PM--profile docker because the docker daemon is not working. checking docker ps gives the message Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Didn’t have an easy fix. I suppose it’s got to do with the docker in docker thingy, but I haven’t experienced this before.
In order to answer your message I’ve double checked with the .devcontainer used in the nf-core modules repo, and it’s different from the one shipped with the pipeline template, in particular the modules one has these features:
"features": {
"<http://ghcr.io/devcontainers/features/github-cli:1.0.11|ghcr.io/devcontainers/features/github-cli:1.0.11>": {
"digest": "sha256:464564228ccdd6028f01f8a62a3cfbaf76e9ba7953b29ac0e53ba2c262604312"
},
"<http://ghcr.io/devcontainers/features/docker-in-docker:2.9.2|ghcr.io/devcontainers/features/docker-in-docker:2.9.2>": {
"digest": "sha256:9074d8eaf4585ab1498c81a8762078992725614fc7a9cfafe799aa22717a6bbf"
}
}
and when spinning up a codespace with this one, the docker daemon works.
I’ve tested it by adding these to the devcontainer.json in the nf-core pipeline’s fork, and the docker daemon works.
so it might be perhaps be an easy fix to the next template release? and/or inform pipeline developers in the meanwhile.
this is only important to run nf-tests when developing local modules or local workflows in a pipeline I suppose, but it prevents from testing them with docker.
I’d be quite in favour of running all conda, docker, singularity before making a pull request, even if it’s local modules.
I didn’t notice this difference in the devcontainer.json definition until now, so during the hackathon I’ve developed in gitpod where the problem doesn’t appear. hence my message here.Phil Ewels
04/04/2025, 10:45 PMPhil Ewels
04/04/2025, 10:46 PMPhil Ewels
04/04/2025, 10:49 PMMahesh Binzer-Panchal
04/07/2025, 7:23 AM