Quoting Trent W. Buck ([email protected]): > Serge Hallyn <[email protected]> > writes: > > > Next, upstart's mountall consults /lib/init/fstab. That's the one > > which will usually prevent container startup from proceeding. The > > lxcguest package for ubuntu will force upstart to mount an empty > > version of that file before mountall runs. So if you install lxcguest > > then mountall can safely run, which makes your container safer against > > package updates. > > Interesting approach. IIRC I just > > dpkg-divert --rename /lib/init/fstab > :> /lib/init/fstab
Yeah that can be a good trick. That doesn't meet my goal, though, of having a single disk image able to boot both as container and kvm host (and physical host). Which is particularly useful when dealing with something like openstack, where Chuck now has a single image which is used to fire off both kvm based and libvirt-lxc based images. thanks, -serge
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev
_______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
