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

[Andrey Repin]

Greetings, Fajar A. Nugraha!

>> # dpkg --list \*lxc\* \*apparmor\*
>> Desired=Unknown/Install/Remove/Purge/Hold
>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name               Version            Description
>> +++-==================-==================-====================================================
>> ii  apparmor           2.7.102-0ubuntu3.1 User-space parser utility for AppArmor

> Is this ubuntu precise?

Yup. 12.04
Both host and guest. Running Trusty LTS kernel. 3.13-something.

> I had some intermittent problems with ubuntu precise containers
> (different one from yours though, my containers would sometime hand
> during startup with "Give root password for maintenance"), and ended
> upgrading both the host and and the container to trusty. Never had the
> problem again since. Might not be a feasible solution for you, but at
> least it's something to think about.

> Anyway, http://packages.ubuntu.com/search?keywords=apparmor says
> latest apparmor is on 2.7.102-0ubuntu3.10, so you might want to
> upgrade (or was it just output trucation issue, and you're already
> running 2.7.102-0ubuntu3.10?)

It is, the list isn't configurable, and I forgot to pull it through pipe to
get more space. Here, this one should be a little better.

# dpkg --list \*lxc\* \*apparmor\* \*cgmanager\* | cat -
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name              Version                           Description
+++-=================-=================================-======================================================
ii  apparmor          2.7.102-0ubuntu3.10               User-space parser utility for AppArmor
ii  apparmor-docs     2.7.102-0ubuntu3.10               Documentation for AppArmor
ii  apparmor-profiles 2.7.102-0ubuntu3.10               Profiles for AppArmor Security policies
ii  apparmor-utils    2.7.102-0ubuntu3.10               Utilities for controlling AppArmor
ii  cgmanager         0.37-1ubuntu1~ubuntu12.04.1~ppa1  Central cgroup manager daemon
ii  dh-apparmor       2.7.102-0ubuntu3.10               AppArmor debhelper routines
ii  libapparmor-perl  2.7.102-0ubuntu3.10               AppArmor library Perl bindings
ii  libapparmor1      2.7.102-0ubuntu3.10               changehat AppArmor library
ii  libcgmanager0     0.37-1ubuntu1~ubuntu12.04.1~ppa1  Central cgroup manager daemon (client library)
ii  liblxc1           1.1.2-0ubuntu3~ubuntu12.04.1~ppa1 Linux Containers userspace tools (library)
ii  lxc               1.1.2-0ubuntu3~ubuntu12.04.1~ppa1 Linux Containers userspace tools
ii  lxc-templates     1.1.3-0ubuntu1~ubuntu12.04.1~ppa1 Linux Containers userspace tools (templates)
ii  lxcfs             0.10-0ubuntu1~ubuntu12.04.1~ppa1  FUSE based filesystem for LXC
ii  python3-lxc       1.1.2-0ubuntu3~ubuntu12.04.1~ppa1 Linux Containers userspace tools (Python 3.x bindings)

>> ii  liblxc1            1.1.2-0ubuntu3~ubu Linux Containers userspace tools (library)
>> ii  lxc                1.1.2-0ubuntu3~ubu Linux Containers userspace tools

> What lxc version did you say you were using?

Were using - 1.1.2.
Then I got an upgrade and my DC didn't came up after a host reboot.
Had to roll back to 1.1.2 to recover operation.

> You said "why 1.1.2 start fine", so I had thought you were using
> 1.1.3. Yet those lines show you're still using 1.1.2. If 1.1.2 works
> fine, then what version are you having problems with?

LXC 1.1.3 - doesn't start with system boot, nor after boot.

>> ii  lxc-templates      1.1.3-0ubuntu1~ubu Linux Containers userspace tools (templates)

> ... and that one has a different version all by itself.

Yes. As it is a supplementary package, I didn't roll it back.

>> ii  lxcfs              0.10-0ubuntu1~ubun FUSE based filesystem for LXC

> If you use ppa:ubuntu-lxc/lxc-stable,

I do.

> the simplest "fix" would probably be to run "apt-get upgrade" (which should
> upgrade everything, including lxc to 1.1.3),

And break it again, third time in a row?...

> verify that packages are up to date (including cgmanager, which should be on
> 0.37),

It is (see above).

> and then reboot.

That's how I landed at current situation.
God bless my preparations, I had a backup plan to login to the host after
container did not start with a reboot.
And God bless apt cache, I were able to downgrade LXC to get container back
running.


-- 
With best regards,
Andrey Repin
Monday, October 5, 2015 17:02:29

Sorry for my terrible english...