On 09/22/2015 08:08 AM, Guido Jäkel wrote:
* Do you use lxc.network.veth.pair to name the hosts side of the veth?
Yes. I rename the veth interfaces to match the names of the containers.
* Was the Container up and running "just before" and you (re)start it within
less than 5min?
Yes. When
On Wed, Sep 23, 2015 at 8:24 AM, Peter Steele wrote:
> On 09/22/2015 08:08 AM, Guido Jäkel wrote:
>>
>> * Do you use lxc.network.veth.pair to name the hosts side of the veth?
>
> Yes. I rename the veth interfaces to match the names of the containers.
>>
>> * Was the
Hi folks!
Interested in LXC container quota support for root fs which is loop
mounted from image.
Tried to use lxc.rootfs.options, but without luck.
Tried to remount / with jqfmt=vfsv0... and it remounts successfully,
buth then quota utilities don't like /dev/loopX from /proc/mounts
because
Dear Peter,
* Do you use lxc.network.veth.pair to name the hosts side of the veth?
* Was the Container up and running "just before" and you (re)start it within
less than 5min?
greetings
Guido
___
lxc-users mailing list
Check /proc/self/mountinfo.
/proc/self/mounts actually also shows the truth. I don't know why
'mount' is lying.
As for it being ro, I do see this as a step down. If you look
at /etc/apparmor.d/abstractions/lxc/container-base you see the
lengths the policy went to to allow writes only to the