ERROR : Requesting capability set 0x000001ffffffffff while permitted capability set is 0x0000003fffffffff

[jpfeuffer]

Using your 3.11.0 image on a hosted GitHub Actions runner.

see https://github.com/OpenMS/OpenMS/actions/runs/4495601964/jobs/7909390460

[vsoch]

You shouldn't need to dockerize singularity for GitHub actions - try just installing it to the runner. https://github.com/singularityhub/install-singularity

[jpfeuffer]

Thank you! I will give it a try.

[jpfeuffer]

It worked by the way. Thanks.

[fcasson]

I have the same issue. I need a docker image with singularity for gitlab CI tests on the docker runner executor

[vsoch]

Based on the error being about permissions, you'd need to run it in privileged mode I think?

[fcasson]

I did run it in privileged mode, but maybe its a problem with my docker daemon env (ubuntu on WSL2, during "hello world" prep before gitlab GI)

[jpfeuffer]

Hi. Maybe my corresponding issue at singularity helps you: https://github.com/sylabs/singularity/issues/1466

TLDR: Github runners do not have a recent enough daemon version. But as always, GitHub is ignoring community feedback: https://github.com/actions/runner-images/issues/7332 https://github.com/actions/runner-images/issues/7042

[fcasson]

Thanks for the link, I had not found it. I am not using GitHub actions, but trying to do something similar on GitLab CI using the Docker executor for runners.

Anyway my first tests before moving to gitlab CI (where I found the issue) were just locally on my laptop (in Ubunutu on WSL2). If I understand the title of that issue correctly, updating my Docker version >= 23 should help?

Will post some simple steps to reproduce later when I am back at the laptop.

EDIT: Upgrading from Docker 20 to Docker 24 fixed the issue for me on Ubuntu / WSL2. A collegue could not reproduce the issue with Docker 20, so it does seem to depend on the env in which the docker daemon is running.

EDIT2: From this links above, it also looks like downgrading the singularity version might also help, but since I have a solution by upgrading docker, I won't need to try that route.

[jpfeuffer]

Yes, correct, I would try that.

[fcasson]

For posterity, here's a oneliner to reproduce the error (on some systems) on docker versions < 23

docker run --privileged quay.io/singularity/singularity:v3.11.0 run docker://alpine

[maawoo]

EDIT2: From this links above, it also looks like downgrading the singularity version might also help, but since I have a solution by upgrading docker, I won't need to try that route.

Downgrading to v3.10 worked for me on Docker v24.0.2: