I have a number of LVM partitions, each containing an Ubuntu installation. Occasionally, I want to do an apt-get dist-upgrade
, to update an installation to the most recent packages. I do this with chroot - the process is usually something like:
$ sudo mount /dev/local/chroot-0 /mnt/chroot-0
$ sudo chroot /mnt/chroot-0 sh -c 'apt-get update && apt-get dist-upgrade'
$ sudo umount /mnt/chroot-0
[ not shown: I also mount and unmount /mnt/chroot-0/{dev,sys,proc}
as bind-mounts to the real /dev
, /sys
and /proc
, as the dist-upgrade seems to expect these to be present ]
However, after upgrading to precise, this process no longer works - the final umount will fail because there are still open files on the /mnt/chroot-0
filesystem. lsof
confirms that there are processes with open files in the chroot. These processes have been started during the dist-upgrade, I'm assuming this is because certain services in the chroot need to be restarted (eg, through service postgresql restart
) after the package is upgraded.
So, I figure I need to tell upstart to stop all the services that are running within this chroot. Is there a way to reliably do this?
I've tried:
cat <<EOF | sudo chroot /mnt/chroot-0 /bin/sh
# stop 'initctl' services
initctl list | awk '/start\/running/ {print \$1}' | xargs -n1 -r initctl stop
EOF
Where initctl list
seems to do the right thing and only list processes that have been started in this particular root. I've tried adding this too, as suggested by Tuminoid:
cat <<EOF | sudo chroot /mnt/chroot-0 /bin/sh
# stop 'service' services
service --status-all 2>/dev/null |
awk '/^ \[ \+ \]/ { print \$4}' |
while read s; do service \$s stop; done
EOF
However, these doesn't seem to catch everything; processes that have daemonised and been reparented to PID 1 don't get stopped. I've also tried:
sudo chroot /mnt/chroot-0 telinit 0
But in this case, init doesn't distinguish between the separate roots and shuts down the entire machine.
So, is there any way to tell init to stop all processes in a particular chroot, so that I can safely unmount the filesystem? Does upstart have any facility to SIGTERM/SIGKILL all child processes (as would be done during regular shutdown) within a chroot?
I don't trust anything but the kernel to keep a sane state here, so I don't (ab)use init to get this job done, nor do I count on myself actually knowing what is or isn't mounted (some packages can mount extra filesystems, like binfmt_misc). So, for process slaughter, I use:
And for umounting chroots, I use:
As an addendum, I'd point out that approaching this as an init problem is probably the wrong way to look at it, unless you actually have an init in the chroot and a separate process space (ie: in the case of LXC containers). With a single init (outside the chroot), and a shared process space, this is no longer "init's problem", but rather just up to you to find the processes that happen to have the offending path, hence the above proc walk.
It's not clear from your initial post if these are fully-bootable systems that you're just upgrading externally (which is how I read it), or if they're chroots that you use for things like package builds. If it's the latter, you might also want a policy-rc.d in place (like the one dropped in by mk-sbuild) that just forbids init jobs starting in the first place. Obviously, that's not a sane solution if these are meant to be bootable systems as well.
You already identified the problem yourself: Some things run
service ...
during dist-upgrade andservice
isn't part of Upstart, but part ofsysvinit
. Add similar awk magic aroundservice --status-all
to stop sysvinit services as you used for Upstart services.I know this question is pretty old, but I think it is as relevant today as it was in 2012, and hopefully someone finds this code useful. I wrote the code for something I was doing, but thought I'd share it.
My code is different, but the ideas are very similar to @infinity (in fact - the only reason I now know about /proc/*/root is because of his answer - thanks @infinity!). I also added some cool additional functionality
Now you would do 2 things to make sure chroot can be unmounted:
Kill all processes that may be running in the chroot:
Kill all processes that may be running outside of the chroot, but interfering with it (ex: if your chroot is /mnt/chroot and dd is writing to /mnt/chroot/testfile, /mnt/chroot will fail to unmount)
Note: Run all code as root
Also, for a less complex version, replace KILL_PID with either
kill -SIGTERM
orkill -SIGKILL
jchroot: a chroot with more isolation.
After your command has been executed, any process started by the execution of this command will be killed, any IPC will be freed, any mount point will be unmounted. All clean!
schroot is not yet able to do this, but this is planned
I have tested it successfully in OpenVZ VPS, which can not use docker or lxc.
Please read the author's blog for the details:
https://vincent.bernat.im/en/blog/2011-jchroot-isolation.html
Just a contracted version of the chosen answer
Regex may be used to address multiple chroots at once.
Kill all processes in single or multiple $CHROOTS.
bash
perl (faster)
Umount single $CHROOT recursively.
bash
Umount multiple $CHROOTS recursively.
bash
schroot: It has the feature of session management. When you stop the session its all processes are killed.
https://github.com/dnschneid/crouton/blob/master/host-bin/unmount-chroot: This scripts kill all the chroot process and unmounts all the mounted devices.