On 04/23/2013 10:51 PM, Stéphane Graber wrote: > If we don't set the block device as lxc.rootfs, then the host has to > mount the LVM outside of the container's mount namespace, which we > prefer not to have to do, especially as you get into a chicken and egg > problem where the LVM path is set in the file that's stored on an > unmounted LVM partition :)
Yes, that's true. My question is that this setup will be possible? That's new to me, as right now AFAIK a rootfs can be only a directory. > We won't prevent you from putting your container on whatever storage you > want and setting lxc.rootfs to a standard fs path. That'll still work, My problem is that creating a 'standard' container with official tools will be pretty complicated. Standard means here, that lxc-create sets up correct configuration files, the guest OS is fine tuned, volume is created...etc. Now it's easy, nice and comfortable, lightweight as the whole project. > it's just that clone won't detect it's LVM backed and so won't create a > new LV (instead it'll just create a new entry under /var/lib/lxc and > rsync the content). That's correct and clear. tamas ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
