Skip to content

Update install.sh - #634

Closed
mribeirodantas wants to merge 4 commits into
masterfrom
fix-apptainer-in-container
Closed

mribeirodantas wants to merge 4 commits into
masterfrom
fix-apptainer-in-container

Conversation

@mribeirodantas

Copy link
Copy Markdown
Member

The apptainer install.sh script is apparently failing silently. This fix should make Apptainer work again inside the container image.

The apptainer `install.sh` script is apparently failing silently. This fix should make Apptainer work again inside the container image.
@netlify

netlify Bot commented Jul 18, 2025

Copy link
Copy Markdown

Deploy Preview for nextflow-training ready!

Name Link
🔨 Latest commit 5fa85ea
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-training/deploys/68f8d3c608fc1c0007704398
😎 Deploy Preview https://deploy-preview-634--nextflow-training.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mribeirodantas mribeirodantas linked an issue Jul 18, 2025 that may be closed by this pull request
@nathanweeks

nathanweeks commented Aug 21, 2025

Copy link
Copy Markdown

I verified that this PR results in a successful apptainer installation.

However, I ran into the following error when attempting to use apptainer in a codespace (using the "codespaces-dev" dev container, i.e. .devcontainer/codespaces-dev/devcontainer.json) :

/tmp -> apptainer pull docker://docker.io/library/ubuntu:24.04
...
/tmp -> apptainer exec ubuntu_24.04.sif cat /etc/os-release
INFO   : A system administrator may need to enable user namespaces, install
INFO   :   apptainer-suid, or compile with ./mconfig --with-suid
ERROR  : Failed to create user namespace: user namespace requires to set /proc/sys/kernel/unprivileged_userns_clone to 1
/tmp -> cat /proc/sys/kernel/unprivileged_userns_clone
1       

Ultimately the following dev container runArgs were required to resolve all errors with the above apptainer exec command:

    "runArgs": [
        "--device=/dev/fuse",
        "--security-opt=seccomp=unconfined",
        "--security-opt=apparmor=unconfined"
    ],

For the "local-dev" dev container (.devcontainer/local-dev/devcontainer.json), the following sufficed in my environment---RockyLinux 8.10 with rootless Podman:

    "runArgs": [
        "--device=/dev/fuse"
    ],

though the other two --security-opt... options did no harm. (Note the "docker-outside-of-docker" feature does not appear to be immediately compatible with rootless podman, and was commented out).

@vdauwera

vdauwera commented Sep 3, 2025

Copy link
Copy Markdown
Collaborator

What's the status of this? Is it still needed, and if so what do we need to get it done?

@vdauwera vdauwera added the environment Devcontainer, codespaces etc label Sep 3, 2025
@vdauwera

Copy link
Copy Markdown
Collaborator

@mribeirodantas Is this good to go?

@mribeirodantas

Copy link
Copy Markdown
Member Author

Actually, no. Singularity is not even being installed anymore :|. As the only training using singularity is the archived one, I think we can close this with wontfix.

@vdauwera vdauwera added the wontfix This will not be worked on label Oct 27, 2025
@vdauwera

Copy link
Copy Markdown
Collaborator

Dropping this

@vdauwera vdauwera closed this Oct 27, 2025
@ewels
ewels deleted the fix-apptainer-in-container branch November 7, 2025 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

environment Devcontainer, codespaces etc wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Apptainer not working in container

3 participants