Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't mount image /proc/self/fd/8: failed to find loop device #2540

Closed
ryzenX opened this issue Jan 13, 2019 · 4 comments
Closed

can't mount image /proc/self/fd/8: failed to find loop device #2540

ryzenX opened this issue Jan 13, 2019 · 4 comments
Assignees

Comments

@ryzenX
Copy link

ryzenX commented Jan 13, 2019

Version of Singularity:

3.0.2-96.gd61d61e2

Expected behavior

I want to run singularity image

Actual behavior

When i want to run singularity image i have this error :
FATAL:   container creation failed: mount error: can't mount image /proc/self/fd/8: failed to find loop device: could not attach image file too loop device: No loop devices available

Steps to reproduce behavior

create Singularity file like this :
https://github.com/truatpasteurdotfr/singularity-alpine/blob/master/Singularity

build image with this command :
sudo singularity build alpinelinux.img Singularity

and try to run like this :
singularity run alpinelinux.img

I have no this error with stable version 3.0
But with last master version it's not work in my computer

i see same problem in gitbuh :
sylabs/singularity#2282

i'm on archlinux, i have brtfs filesystem (not NFS) and i have not enable ecl (i not modify conf file)

@jscook2345 jscook2345 self-assigned this Jan 16, 2019
@jscook2345
Copy link
Contributor

@ryzenX

I've had this happen on a VM with opensuse where I upgraded the kernel but did not reload the vagrant VM.

Are you running your build in a VM?

@ryzenX
Copy link
Author

ryzenX commented Jan 16, 2019

yes i'm on VM with virtualbox
But i not use Vagrant

i must downgrade linux kernel (if yes, what version linux kernel i must use) ? or may be have other solution ?

@cclerget
Copy link
Collaborator

@ryzenX Did you reboot your VM to load updated kernel ? Same happens to me after upgrade, you need to reboot to fix that, to ensure this is not a Singularity you can try to load an image :

sudo losetup -f alpinelinux.img
losetup -a

If you have an error or you don't see an image associated with a loop device, that means kernel module autoload can't find a module for your running kernel since the upgrade remove it from /lib/modules to replace it with upgraded kernel version

@ryzenX
Copy link
Author

ryzenX commented Jan 17, 2019

ok, i rebooted my vm and it's work.
thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants