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
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 ha
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):
> 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
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 0
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
lxc-star
