On Fri, Sep 13, 2013 at 10:16 PM, Fajar A. Nugraha l...@fajar.net wrote:
On Fri, Sep 13, 2013 at 7:43 PM, Serge Hallyn serge.hal...@ubuntu.comwrote:
I'm wondering
whether it could just be that there is a socket waiting for a tcp
timeout, holding the veth open.
It may be the case.
Hello
In Ubuntu 12.04 I used to be able to create containers with this line in
the container's fstab:
proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0
Now in 13.04 I get the following error:
$ sudo lxc-start -n test -f /var/lib/lxc/test/lxc.conf -lDEBUG -L
/dev/stdout
Ubuntu 13.04 comes with lxc 0.9?
I used same version (from debian testing) on wheezy and I have no
problem with read only proc.
And my mount options are the same as yours, strange.
lxc.mount.entry = proc
/srv/vserver/vs-db01-dev/rootfs/proc proc nodev,noexec,nosuid,ro
Hi Serge
On 09/18/2013 01:55 PM, Serge Hallyn wrote:
An unfortunate known bug - try the package in raring-proposed.
(You'll need lxc-start to be running unconfined as well, but if
that worked for you in precise I assume you already have that).
I am using that package (I reported those ipv6
Quoting Andre Nathan (an...@digirati.com.br):
Hi Serge
On 09/18/2013 01:55 PM, Serge Hallyn wrote:
An unfortunate known bug - try the package in raring-proposed.
(You'll need lxc-start to be running unconfined as well, but if
that worked for you in precise I assume you already have
On 09/18/2013 03:48 PM, Serge Hallyn wrote:
Double-d'oh. The package in raring-proposed doesn't yet have the needed
fix, which is below. It's in upstream git. Do you mind opening a new
bug so we can SRU this?
Done: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1227313
Cheers,
Andre
On 18/09/13 16:43, Gary Ballantyne wrote:
I am pretty sure that XFS needs to be *initially* mounted with the quota
option --- but after rebooting I have lost the uquota.
Update:
If I create an ordinary (not lvm backed) container, then shuffle things
around so that /var/lib/lxc/vm0/rootfs is
