Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Singularity container creation failure due to failure to mount squashfs #359

Open
alfpark opened this issue Oct 16, 2020 · 0 comments
Open
Assignees
Labels

Comments

@alfpark
Copy link
Collaborator

alfpark commented Oct 16, 2020

Problem Description

Singularity containers do not start properly due to a change in mount for newer kernels:

FATAL:  container creation failed: mount /proc/self/fd/3->/mnt/singularity/mnt/session/rootfs error: while mounting image /proc/self/fd/3: kernel reported a bad superblock for squashfs image partition, possible causes are that your kernel doesn't support the compression algorithm or the image is corrupted

Batch Shipyard Version

3.9.1

Other Comments

See apptainer/singularity#4801

@alfpark alfpark added the defect label Oct 16, 2020
@alfpark alfpark self-assigned this Oct 16, 2020
alfpark added a commit that referenced this issue Apr 26, 2021
- Drop support for Python < 3.6, resolves #264
- Update Singularity to 3.7.3, resolves #359
- Update and fix shellcheck issues
- Remove nodeps
- Create separate Singularity image replication pipeline
- Move code sign to CI
- Remove Travis CI
alfpark added a commit that referenced this issue Mar 20, 2023
- Drop support for Python < 3.6, resolves #264
- Update Singularity to 3.7.3, resolves #359
- Update and fix shellcheck issues
- Remove nodeps
- Create separate Singularity image replication pipeline
- Move code sign to CI
- Remove Travis CI
alfpark added a commit that referenced this issue Mar 20, 2023
- Drop support for Python < 3.6, resolves #264
- Update Singularity to 3.7.3, resolves #359
- Update and fix shellcheck issues
- Remove nodeps
- Create separate Singularity image replication pipeline
- Move code sign to CI
- Remove Travis CI
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant