[issue659] grml-chroot does not properly handle multiple chroots

Michael Prokop bts at bts.grml.org
Fri Jan 13 03:09:34 CET 2012


Michael Prokop <mika at grml.org> added the comment:

After another round of discussion we sadly had to decide this isn't really
bullet proof though.

Quoting Gebi from the according discussion on IRC (with his permission):
    
02:48 < gebi> you know that /tmp was to bind mounted too if you want to use X?
02:49 < gebi> not a good idea to use a bind mounted /tmp inside of the chroot
for saving state which ultimatly goes back to the base image
02:50 < gebi> mrud: but you e.g HAVE to mount --bind /tmp chroot/tmp to use X in
chroot
02:51 < gebi> so it would be no fun to use chroot/tmp as state dir for
grml-chroot, because on unmounting your files would not be there anymore
02:51 < gebi> because hidden by the mount --bind

So unless someone provides a tested and bullet proof solution we've to close
this with won't fix.

----------
messages: 2127, 2128, 2129, 2131, 2132, 2170, 3036, 3242, 3847, 4247, 4248
nosy: gebi, mru, zugschlus
priority: wish
status: wont-fix
title: grml-chroot does not properly handle multiple chroots

_____________________________________
GRML issue tracker <bts at bts.grml.org>
<http://bts.grml.org/grml/issue659>
_____________________________________


More information about the Bugs-changes mailing list