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
The last few days we have been seeing a lot more apptainer e2e failures with loop device errors, for example in #1185run 5, with messages for example like
FATAL: container creation failed: mount hook function failure: mount /proc/self/fd/3->/usr/local/var/apptainer/mnt/session/rootfs error: while mounting image /proc/self/fd/3: failed to find loop device: could not attach image file to loop device: failed to attach loop device: could not open /dev/loop9: no such device or address
This may be related to the problem found in sylabs/singularity#1499 and also reported at #1258, except the error message is different, apptainer is already using /dev/loop-control so the solution provided by sylabs does not apply, and the apptainer e2e tests run on ubuntu 22, not ubuntu 20.
The text was updated successfully, but these errors were encountered:
FATAL: container creation failed: mount /proc/self/fd/3->/var/lib/singularity/mnt/session/rootfs error: while mounting image /proc/self/fd/3: failed to find loop device: could not attach image file to loop device: no loop devices available
The last few days we have been seeing a lot more apptainer e2e failures with loop device errors, for example in #1185 run 5, with messages for example like
This may be related to the problem found in sylabs/singularity#1499 and also reported at #1258, except the error message is different, apptainer is already using /dev/loop-control so the solution provided by sylabs does not apply, and the apptainer e2e tests run on ubuntu 22, not ubuntu 20.
The text was updated successfully, but these errors were encountered: