Docker/AppArmor not working properly after update to ProxMox kernel

  • Hey everyone,


    I plan on changing my network card from AQC100 to RTL8126. In preparation for this, I decided to change the kernel with the built in tool to the latest ProxMox kernel 6.8, as it should have native support for the new NIC.


    After rebooting, I noticed a very high system load that did not go down after several minutes. I investigated and found that some of the docker containers I am running behave unexpectedly, thus causing the high system load. I also can't reach my containers from the web.


    Here are the relevant parts of the logs of some of the containers, and the log from dmesg:

    Judging from the logs, it seems like the kernel update caused some unwanted behaviour of apparmor.

    Debian/OMV is running natively on the system, and all packages in my system are up to date. The versions of docker are:
    docker-ce 5:27.3.1-1~debian.12~bookworm and docker-compose-plugin 2.29.7-1~debian.12~bookworm, I am using the OMV compose plugin to manage my containers.

    Rebooting with the old kernel fixes the issue, so that's what I'm doing for now. But still, dmesg is spammed with this message:


    What can I do to resolve this issue, so I can use the latest ProxMox kernel?


    Best regards,

    Bastian

    • New
    • Official Post

    What can I do to resolve this issue,

    The Proxmox kernel is from Ubuntu where apparmor is always running. I would just uninstall the apparmor package (leave libapparmor1 installed) or disable apparmor. Plenty of threads on this forum about how to do that.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • DerSpatz

    Added the Label resolved
  • DerSpatz

    Changed the title of the thread from “Docker not working properly after update to ProxMox kernel” to “Docker/AppArmor not working properly after update to ProxMox kernel”.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!