-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
I'm still getting errors with |
I had a corrupted arch image download, testing now. |
Okay yeah, works fine now, you can ignore my message |
moby/moby#27886 (comment) might be a fix |
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
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.
The text was updated successfully, but these errors were encountered: