docker not working since omv-upgrade

Quote from ryecoaaron

Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):

Code

sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' | sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot

Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

This solution was effective for me as well. One point, of course, on my system there was no need to do the mkdir command as the grub.d directory already exists ...

Thanks ryecoaaron

I've had the same problem on my Odroid HC2, I fixed it by downgrading the docker-ce and docker-ce-cli packages, then restarting the docker service:

sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye
sudo service docker restart

I confirm, I had the same problem.

I installed Docker 5:20.10.23~3-0~debian-bullseye

Portainer is now working, thanks

Quote from NothingNowhere

I've had the same problem on my Odroid HC2, I fixed it by downgrading the docker-ce and docker-ce-cli packages, then restarting the docker service:

Code

sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye
sudo service docker restart

I also confirm this works. Had to re-install Portainer though. It's now back on the default ports (9000 and 8000).

Quote from NothingNowhere

I've had the same problem on my Odroid HC2, I fixed it by downgrading the docker-ce and docker-ce-cli packages, then restarting the docker service:

Code

sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye
sudo service docker restart

Probably the best workaround - reverting the change - until everything is fully understood. Thanks.

WIth armbian, since there's no grub, adding to armbianEnv.txt

extraargs=apparmor=0

and rebooting worked on my Rock64 without having to downgrade. Would imaging should also work on Odroid HC-2, XU4, etc.

Updating grub worked on my other OMV systems with x86 processors.

Quote from ryecoaaron

Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):

Code

sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' | sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot

Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

Thank you for this "fix". I was really worried when restarting docker and trying a reboot didn't cause my containers to restart, especially when I tried docker restart on portainer.

Will this become a pull request for OpenMediaVault and be published in a patch release? Or is AppArmor something that is used by some in the OpenMediaVault community?

Quote from ryecoaaron

Why is it the best? Staying on the same package is only a short term solution. You will have to apt-mark hold docker-ce to prevent it from being upgrade.

I have the same issues today and was thinking this is the best solution also. I understand that AppArmor is initiated on Grub and rolling back will only work till next update, but it seams disabling AppArmor still leaves portainer inoperable?

Quote from spupuz

in my case i have portainer fully functional and apparmor disabled like ryecoaaron has suggested

Thanks

in my case I have portainer fully functional, I just needed to reinstall it as if it were an update after disabling apparmor

Quote from ryecoaaron

Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):

Code

sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' | sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot

Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

Thanks worked here

Not sure why some people are having issues with Portainer. Works fine for me with the apparmor grub change. I agree that rolling back to the older version of docker isn't the best fix as you'll eventually have to update, and since it's a change that came directly from Docker, I wouldn't expect it to magically work later without making some form of change to apparmor.

Considering Portainer is a relatively simple reinstall, I would try that over rolling back to an older Docker. If it still fails, try reinstalling the Portainer container from the CLI to see what could be causing the issue.

Looks like docker FINALLY released the release notes for 23.

Docker Engine 23.0 release notes

"Known issues

Some Debian users have reported issues with containers failing to start after upgrading to the 23.0 version. The error message indicates that the issue is due to a missing apparmor_parser dependency:"

"The workaround to this issue is to install the apparmor-utils package manually:

apt-get install apparmor-utils