[Lxc-users] Read-only container /proc

Serge Hallyn serge.hallyn at ubuntu.com
Wed Sep 18 16:55:26 UTC 2013


Quoting Andre Nathan (andre at 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 test -f /var/lib/lxc/test/lxc.conf -lDEBUG -L
> /dev/stdout
> lxc-start: Permission denied - failed to create symlink for kmsg
> lxc-start: failed to setup kmsg for 'test'
> lxc-start: Read-only file system - failed to change apparmor profile to
> unconfined
> lxc-start: invalid sequence number 1. expected 4
> lxc-start: failed to spawn 'test'
> 
> This happens even when apparmor is disabled for lxc-start.

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).




More information about the lxc-users mailing list