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
$ singularity --version
singularity version 3.7.3-1.el7
Describe the bug
Singularity does not unmount the sif containers after running. After a while, all loop devices are "used up" and I need to unmount them manually to be able to run again.
To Reproduce
$ mount
...
tmpfs on /run/user/1003 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=796564k,mode=700,uid=1003,gid=1003)
$ singularity run shub://GodloveD/lolcow
INFO: Use cached image
___________________
< Are you a turtle? >
-------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
$ mount
...
tmpfs on /run/user/1003 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=796564k,mode=700,uid=1003,gid=1003)
/root/.singularity/cache/shub/a59d8de3121579fe9c95ab8af0297c2e3aefd827 on /run/media/root/disk type squashfs (ro,nosuid,nodev,relatime,seclabel,uhelper=udisks2)
$ singularity run shub://GodloveD/lolcow
INFO: Use cached image
________________________________________
/ You will be advanced socially, without \
\ any special effort on your part. /
----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
$ mount
...
tmpfs on /run/user/1003 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=796564k,mode=700,uid=1003,gid=1003)
/root/.singularity/cache/shub/a59d8de3121579fe9c95ab8af0297c2e3aefd827 on /run/media/root/disk type squashfs (ro,nosuid,nodev,relatime,seclabel,uhelper=udisks2)
/root/.singularity/cache/shub/a59d8de3121579fe9c95ab8af0297c2e3aefd827 on /run/media/root/disk1 type squashfs (ro,nosuid,nodev,relatime,seclabel,uhelper=udisks2)
Expected behavior
The mounted loop devices should be unmounted after the container exits.
I've dropped the bug label here as singularity does not mount anything under /run/media/xxxx. That location is usually managed by a Linux Desktop Environment or associated process, which auto-mounts CDs, inserted USB sticks etc.
Is this a CERN specific customization of CentOS 7? Which desktop environment (if any) is used?
I have done development work on various machines running different versions of GNOME and KDE, and haven't seen this issue.
Singularity does not mount anything under /run/media/xxx so the issue must be due to an external process. In the absence of a way to reproduce, I'll close this as there is nothing we can do here.
Version of Singularity
Describe the bug
Singularity does not unmount the
sif
containers after running. After a while, all loop devices are "used up" and I need to unmount them manually to be able to run again.To Reproduce
Expected behavior
The mounted loop devices should be unmounted after the container exits.
OS / Linux Distribution
Installation Method
Installed via
yum
.Additional context
Running sandboxes does not seem to be causing any problems. Only the
sif
container files.The text was updated successfully, but these errors were encountered: