[lxc-users] How to recover from ERROR state

Kees Bakker keesb at ghs.com
Wed Sep 12 09:08:30 UTC 2018


On 12-09-18 10:51, Fajar A. Nugraha wrote:
> On Wed, Sep 12, 2018 at 3:14 PM, Kees Bakker <keesb at ghs.com <mailto:keesb at ghs.com>> wrote:
>
>     On 11-09-18 21:56, Andrey Repin wrote:
>     > Greetings, Kees Bakker!
>     >
>     >> ii  lxc-common     2.0.8-0ubuntu1~16.04.2  amd64        Linux Containers userspace tools (common tools)
>     >> ii  lxcfs          2.0.8-0ubuntu1~16.04.2  amd64        FUSE based filesystem for LXC
>     >> ii  lxd            2.0.11-0ubuntu1~16.04.4 amd64        Container hypervisor based on LXC - daemon
>     >> ii  lxd-client     2.0.11-0ubuntu1~16.04.4 amd64        Container hypervisor based on LXC - client
>     > Upgrade from PPA.
>     > add-apt-repository ppa:ubuntu-lxc/stable
>     >
>     > ii  lxc-common         2.1.1-0ubuntu1 amd64          Linux Containers userspace tools (common t
>     > ii  lxc-templates      2.1.1-0ubuntu1 amd64          Linux Containers userspace tools (template
>     > ii  lxc1               2.1.1-0ubuntu1 amd64          Linux Containers userspace tools
>     > ii  lxcfs              2.0.8-1ubuntu2 amd64          FUSE based filesystem for LXC
>     >
>     >
>
>     Hmm. That PPA does not have liblxc1 2.1.1, but 3.0.1
>
>     # apt list --upgradable
>     Listing... Done
>     liblxc1/xenial 3.0.1-0ubuntu1~18.04.2~ubuntu16.04.1~ppa1 amd64 [upgradable from: 2.0.8-0ubuntu1~16.04.2]
>     libseccomp2/xenial 2.3.1-2.1ubuntu3~ubuntu16.04.1~ppa1 amd64 [upgradable from: 2.3.1-2.1ubuntu2~16.04.1]
>     lxc-common/xenial 2.1.1-0ubuntu1~ubuntu16.04.1~ppa1 amd64 [upgradable from: 2.0.8-0ubuntu1~16.04.2]
>     lxcfs/xenial 3.0.1-0ubuntu2~18.04.1~ubuntu16.04.1~ppa1 amd64 [upgradable from: 2.0.8-0ubuntu1~16.04.2]
>
>     # apt policy liblxc1
>     liblxc1:
>       Installed: 2.0.8-0ubuntu1~16.04.2
>       Candidate: 3.0.1-0ubuntu1~18.04.2~ubuntu16.04.1~ppa1
>       Version table:
>          3.0.1-0ubuntu1~18.04.2~ubuntu16.04.1~ppa1 500
>             500 http://ppa.launchpad.net/ubuntu-lxc/stable/ubuntu <http://ppa.launchpad.net/ubuntu-lxc/stable/ubuntu> xenial/main amd64 Packages
>          3.0.1-0ubuntu1~16.04.2 100
>             100 http://nl.archive.ubuntu.com/ubuntu <http://nl.archive.ubuntu.com/ubuntu> xenial-backports/main amd64 Packages
>      *** 2.0.8-0ubuntu1~16.04.2 500
>             500 http://nl.archive.ubuntu.com/ubuntu <http://nl.archive.ubuntu.com/ubuntu> xenial-updates/main amd64 Packages
>             100 /var/lib/dpkg/status
>          2.0.7-0ubuntu1~16.04.2 500
>             500 http://security.ubuntu.com/ubuntu <http://security.ubuntu.com/ubuntu> xenial-security/main amd64 Packages
>          2.0.0-0ubuntu2 500
>             500 http://nl.archive.ubuntu.com/ubuntu <http://nl.archive.ubuntu.com/ubuntu> xenial/main amd64 Packages
>
>     I could upgrade to the 3.0 packages, but that would be more challenging.
>
>
>
> 2.1 is not 'LTS' version, so it's expected that it won't be available anymore. Personally I'd upgrade to 3.0. But backup /var/lib/lxd (when ALL containers are stopped) beforehand.

Upgrading to 3.0 gives me two options: 1) xenial-backports, 2) the suggested PPA (ppa:ubuntu-lxc/stable).
Which one would you pick?

>
> FWIW, I'm more inclined to think your 'kworker' issue might be related to btrfs instead of lxd, but it might be harder to debug that.
>

OK, I'll keep that in mind.
-- 
Kees
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20180912/5882633b/attachment.html>


More information about the lxc-users mailing list