On 19.05.2011 11:18, Ulli Horlacher wrote:
>
> But the underlaying partion must be big enouigh to contain all LXC
> containers! How do you prevent to a single container to allocate all free
> disk space?
I had no time to consult the man pages or to just give it try. Have you
tried it? But I guess
On 19.05.2011 09:59, Ulli Horlacher wrote:
>
> But how do you set up quotas for the snapshots?
> One can limit the size of the whole LVM container, but this is the same as
> using a regular disk partition (for all LXC containers).
I'm by no means an lvm expert, but I would have guessed from Hallyn
On 18.05.2011 20:59, Serge Hallyn wrote:
> Certainly not for loopback. Just make sure to create it as having
> a big hole in the middle, something like
>
> dd if=/dev/zero of=/srv/container1.rootfs.img bs=1M skip=1 count=1
>
Cool, I didn't know I can use sparse files for that. Good to know
On 18.05.2011 17:52, Serge Hallyn wrote:
>
> Why do you call it not easy? Because you don't have spare partitions to
> dedicate to a pv? Or because you're not used to using lvm?
>
> If the former, then you could use a loopback filesystem instead of
> an LVM. I assume that'll impact performance,
Hi,
I basically want to have a single vserver installation and start it
several times using different configuration options (mainly for
different network settings). Most important, the files should be
readonly/ immutable from within the vserver instances. What's the best
way to achive this?
I
