-
Notifications
You must be signed in to change notification settings - Fork 158
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
Random losetup errors while building inside mock #238
Comments
Try adding this patch to mock and see if it works better for you: rpm-software-management/mock#107 |
OK, seems pretty good. I have done 3 builds in a row without an issue so far. |
Noticed same error with epel7 mock. Patch fixed the issue here too. |
loop-control creates loop devices under /dev outside mock even if the request is from inside - just add a few loop devices before calling lmc if it's still an issue... something like: |
mock --old-chroot now creates the loop devices even if they aren't present on the host. Closing this. |
I am trying to build a Fedora 26 live image inside mock. For this I am currently using "--old-chroot" option for mock as otherwise /dev/loop does not even exist.
(The -squashfs_args "-noD -noI -noF -noX -no-duplicates" was me trying to speed up mksquashfs, not that it worked.)
The text was updated successfully, but these errors were encountered: