> exec_sudo: device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
One thought is that possibly a daemon or something from the chroot is still running, holding files open somehow. I'm not sure what this would be
I imagine loop0p1 is still around when dib exits. Could you run lsof or similar to see what process is holding the device open? that will give a clue as to what's going on.
Ok, this is saying
> exec_sudo: device-mapper: remove ioctl on loop0p1 failed: Device or resource busy
One thought is that possibly a daemon or something from the chroot is still running, holding files open somehow. I'm not sure what this would be
I imagine loop0p1 is still around when dib exits. Could you run lsof or similar to see what process is holding the device open? that will give a clue as to what's going on.