systemctl status degraded, apparmor.service fails, in fresh Ubuntu 18.04 container

Discussion in 'Proxmox VE: Installation and configuration' started by BenignlyLoopy, Nov 10, 2018.

  1. BenignlyLoopy

    BenignlyLoopy New Member

    Joined:
    Nov 10, 2018
    Messages:
    1
    Likes Received:
    0
    I have several services running on Ubuntu 16.04 containers and was considering moving them to Ubuntu 18.04 containers.

    But (on latest Proxmox version), fresh ubuntu 18.04 containers when booted are showing up as degraded.

    The one failed unit inside the container is apparmor.service:

    Manual attempt to start this service fail. Errors as follows:

    Ubuntu 16.04 containers don't have this problem.

    Any ideas what is going on here?
     
  2. SysAx

    SysAx New Member
    Proxmox VE Subscriber

    Joined:
    Jun 16, 2016
    Messages:
    11
    Likes Received:
    0
    I have the same problem on Ubuntu 16.04 containers after upgrading from proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve) to proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve).

    These containers worked before upgrade and when I move a container on an old node proxmox-ve: 5.2-2, apparmor start without errors.

    Related to this problem, the NFS mounts no longer work from these LXC containers.

    Christian
     
  3. fireon

    fireon Well-Known Member
    Proxmox VE Subscriber

    Joined:
    Oct 25, 2010
    Messages:
    2,731
    Likes Received:
    150
    Had the same problem on upgrading container from 16.04 to 18.04. I solved the problem with:
    Code:
    apt remove apparmor --purge -y
    rm -rf /etc/apparmor*
    apt install apparmor -y
    systemctl restart apparmor.service
    systemctl status apparmor.service
    I have to do that on all containers with Upgrade from 16.04 to 18.04.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. SysAx

    SysAx New Member
    Proxmox VE Subscriber

    Joined:
    Jun 16, 2016
    Messages:
    11
    Likes Received:
    0
    Thanks Fireon, it works for me on Ubuntu 16.04.

    Regards,
    Christian
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice