You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
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
- 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
- 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
- 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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem Description
Singularity containers do not start properly due to a change in mount for newer kernels:
Batch Shipyard Version
3.9.1
Other Comments
See apptainer/singularity#4801
The text was updated successfully, but these errors were encountered: