[lxc-users] LXC 1.1.3 update blocks container startup.

[Serge Hallyn]

Quoting Andrey Repin (anrdaemon at yandex.ru):
> Greetings, Serge Hallyn!
> 
> > What does 'sudo aa-status' show?
> 
> This is with fully up to date system, including fresh LXC 1.1.3:
> 
> # aa-status
> apparmor module is loaded.
> 7 profiles are loaded.
> 6 profiles are in enforce mode.
>    /sbin/dhclient
>    /usr/lib/NetworkManager/nm-dhcp-client.action
>    /usr/lib/connman/scripts/dhclient-script
>    /usr/lib/cups/backend/cups-pdf
>    /usr/sbin/cupsd
>    /usr/sbin/mysqld
> 1 profiles are in complain mode.
>    /usr/sbin/ntpd
> 3 processes have profiles defined.
> 2 processes are in enforce mode.
>    /usr/sbin/cupsd (1165)
>    /usr/sbin/mysqld (1605)
> 1 processes are in complain mode.
>    /usr/sbin/ntpd (1872)
> 0 processes are unconfined but have a profile defined.

Right no lxc profile shere.

> > #!/usr/bin/python3
> > import lxc
> > c = lxc.Container("dc1-1")
> > c.get_config_item("lxc.aa_profile")
> 
> This still throws an error, but if I change the container name to
> 
> > #!/usr/bin/python3
> > import lxc
> > c = lxc.Container("dc1")
> > c.get_config_item("lxc.aa_profile")
> 
> It executes silently and do not return any output. (Which, I presume, was one
> of the desired outcomes?)

Right that means 'use the default' which will be lxc-container-default.