On Tue, Feb 07, 2017 at 03:08:58PM -0500, Rich Freeman wrote > I suspect sticking something like this before the chroot command might > do the trick: > unshare -p -f --mount-proc -m -i -u > > That will create a new PID, mount, IPC, and UTS namespace for the > chroot. If you do the mounts after this then when the process exists > any mounts will disappear. If you run ps -ea inside you'll see your > shell running as pid 1. Now, if you set up your mounts before running > unshare then they'll stick around since they were set up in the host > namespace and not the container.
Is the command sequence... unshare -p -f --mount-proc -m -i -u mount --bind /dev/ /home/misc/centos65/dev/ mount --bind /proc/ /home/misc/centos65/proc/ linux32 chroot /home/misc/centos65/ /bin/bash -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
