Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqubes-builder leaves unmounted filesystems #2440
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Nov 18, 2016
Member
This is intentional behavior, see QubesOS/qubes-builder@74c2d04 for reasoning.
If you want to cleanup - see make clean targets (make help can be of use). It will umount what's needed first. Also you can just call make umount.
|
This is intentional behavior, see QubesOS/qubes-builder@74c2d04 for reasoning. |
marmarek
closed this
Nov 18, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tezeb commentedNov 18, 2016
When building templates(tested on archlinux, but looking at Makefile it seems that it affects all dists), after build is finished mounts done during dist-prepare-chroot make target are not unmounted. As there are even 3 scripts for handling unmounts(#1157), it would be nice to use them.
The issue is that cleaning repo(ie. rm -Rf) requires using sudo, as there are root owned files inside(chroot-contents), but using it with proc/sys etc mounted is probably not the best idea.
This happens when building Archlinux template for Qubes R3.2.
Expected behavior:
make COMPONENT-vmshall not leave fs mountedActual behavior:
make COMPONENT-vmleaves all dist specific directories mountedSteps to reproduce the behavior:
in qubes-builder, run
./setup
make qubes-vm