Re: [lxc-devel] [PATCH] implement loopback backing store

2013-06-05 Thread Tomas Pospisek
Am 03.06.2013 23:38, schrieb Serge Hallyn: > Create a loopfile backed container by doing: > > lxc-create -B loop -t template -n name > > or > > lxc-clone -B loop -o dir1 -n loop1 > > The rootfs in the configuration file will be > > loop:/var/lib/lxc/loop1/rootdev While I app

Re: [lxc-devel] [PATCH] implement loopback backing store

2013-06-05 Thread Serge Hallyn
Quoting Tomas Pospisek (t...@sourcepole.ch): > Am 03.06.2013 23:38, schrieb Serge Hallyn: > > Create a loopfile backed container by doing: > > > > lxc-create -B loop -t template -n name > > > > or > > > > lxc-clone -B loop -o dir1 -n loop1 > > > > The rootfs in the configuration file wi

Re: [lxc-devel] [PATCH] implement loopback backing store

2013-06-05 Thread Tomas Pospisek
Am 05.06.2013 14:45, schrieb Serge Hallyn: > Quoting Tomas Pospisek (t...@sourcepole.ch): >> Am 03.06.2013 23:38, schrieb Serge Hallyn: >>> Create a loopfile backed container by doing: >>> >>> lxc-create -B loop -t template -n name >>> >>> or >>> >>> lxc-clone -B loop -o dir1 -n loop1 >>> >

[lxc-devel] [PATCH RFC] lxclock: move container locks into /run/lock

2013-06-05 Thread Serge Hallyn
Currently the lxc API mutexes configuration file read/writes with a lock called $lxcpath/locks/$lxcname. This fails if the container is on a rofs. This patch moves those locks under /run/lock/lxc. The $lxcpath/$lxcname/partial file is not moved - if you can't create it, you probably can't create