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

loopdev #1

Open
westlane opened this issue Mar 20, 2018 · 5 comments
Open

loopdev #1

westlane opened this issue Mar 20, 2018 · 5 comments

Comments

@westlane
Copy link
Member

The first time the container is run it is common to see this:

ls: cannot access '/dev/loop0*1': No such file or directory

This prevents the filesystem from successfully building an image. The second time will typically work as expected.

@jedahan
Copy link

jedahan commented Aug 17, 2018

I'm still getting errors with Could not open /dev/loop0p2: No such device or address after the first try.

@jedahan
Copy link

jedahan commented Aug 17, 2018

I had a corrupted arch image download, testing now.

@jedahan
Copy link

jedahan commented Aug 17, 2018

Okay yeah, works fine now, you can ignore my message

@jedahan
Copy link

jedahan commented Dec 13, 2018

moby/moby#27886 (comment) might be a fix

@jedahan
Copy link

jedahan commented Dec 13, 2018

Also balena-io/balena-cli#1008 which might just require us to bindmount

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

2 participants