chroots can behave weird at times like anything else inside or around a computer or phone.
I noticed you use the mount bind option and I think it's only necessary to bind dev so you can mount dev/pts
( at least up to wheezy anyways ).
If you try another pre chroot mounting scheme it might let you run heavier window managers in the chroot, depending on the chroot host / chroot target combination.
Also be careful about how you mount and than always still be on the lookout for undesired changes to the host system
that occur back from the chroot. It happens even though it's not supposed to.
While typing this I just thought of a way to try to remove the bind option from the mount /dev command as well,, by copying the devs from the host system into place,, pre chroot than seeing if the chroot still works correctly.
Another thing to remember is the chroot target will behave almost exactly like the chroot host garrrrr
If anyone knows howto run a chroot target that runs a different ARCH from the chroot host - Please write it up !
Code: Select all
#mount -t devtmpfs /dev $chrootdir/dev -o bind
I also mount
Code: Select all
#mount -t devpts /dev/pts $chrootdir/dev/pts
#mount -t tmpfs /dev/shm $chrootdir/dev/shm
because networking usually didn't work without it ( the way I premount the chroot env )
as you'll notice when running
system mountpoints are changing a lot
I think squeeze to wheezy changed /dev/shm to /run/shm
and I haven't fiddled enough yet to know what's needed now and what's not
Edit Jan 18 21:19:07 EST 2018
double check the debootstrap man files Examples section for more hints
-keep in mind that the Examples section can show differences DEPENDING on which Debian Version you are viewing the man page from!
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.