docker not working since omv-upgrade

Quote from ParadingLunatic

Looks like docker FINALLY released the release notes for 23.

https://docs.docker.com/engine/release-notes/23.0/

"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:

Code

apt-get install apparmor-utils

Display More

Thanks. All perfect

Quote from ryecoaaron

I run almost all of my containers on ubuntu with apparmor. It might be time to stop fighting apparmor on OMV. I might have to do some testing.

I think thats the best path forward!

Kinda had a feeling apparmor-utils would install apparmor as well.

I did notice that on my headless debian system I didn't have any issues with the upgrade, which obviously has apparmor running.

Either way, thanks for all the testing/work you do for OMV! Definitely appreciate it!

@ryecoaaron Quick question about zfs, I believe it used to show up as Services in the dashboard, however its not showing up in the Services anymore, could be because of I was trying to troubleshoot this morning and installed and uninstalled bunch of stuff.

ZFS is working as expected but I am not sure if it showed as service or not...

Quote from ryecoaaron

Not sure how this is related to docker and apparmor but on OMV 6.x, it has always been in the Storage section. If the plugin is fully installed with status of 'ii', then hit ctrl-shift-R. If that still doesn't show it, sudo omv-mkworkbench all

Its absolutely not related to docker and apparmor, I maybe mistaken but remember seeing it in services, could be wrong, but as you said its in the storage section and its working. I was asking because while troubleshooting I made changes and if that impacted it...

Good afternoon!

Now I installed the apparmor-utils, restarted the docker and everything worked for me.

In the future, I may have some problems with docker? Maybe it's better for me to remove the apparmor-utils now and disable the apparmor in system?

Yeah this is not the sh^& I want to come home to and deal with, so THANK YOU FOR figuring it out for us!

The apparmor-utils worked for me, no idea what it is or means, but it did.

Thank you ryecoaaron for your solution/workaround. Portainer still works for me.

Thank you all who figured out what to do to solve the problem

I manually installed the apparmor package and managed to start docker/portainer again (and btw took the chance to do the long postponed update from OMV5 to OMV6 ).

ok, fixed the problem with:

apt install apparmor apparmor-utils auditd

everything works again.

Installed from the ISO a few weeks ago and had no problems since than.

Now i will install the Kernel-Plugin to make Backups with Clonezilla.

Did not noticed OMV is against apparmour.

Is there a reason for it?

All my containers work perfectly fine again.

So if nothing new comes up i will go with apparmour.

I still cannot access the portainer UI even after installing apparmor

Quote from pendragon666

I still cannot access the portainer UI even after installing apparmor

If you manually installed apparmor/apparmor-utils you probably also need to "reinstall" Portainer via the OMV webinterface with AppArmor enabled, then you should be able to access it once again. I just did exactly that and it worked for me.

The status for Portainer shown in the OMV webinterface should then change from "Created" to "Up [...]".

Quote from Imbon

If you manually installed apparmor/apparmor-utils you probably also need to "reinstall" Portainer via the OMV webinterface with AppArmor enabled, then you should be able to access it once again. I just did exactly that and it worked for me.

The status for Portainer shown in the OMV webinterface should then change from "Created" to "Up [...]".

Thanks, that got it going again.

Quote from Imbon

If you manually installed apparmor/apparmor-utils you probably also need to "reinstall" Portainer via the OMV webinterface with AppArmor enabled, then you should be able to access it once again. I just did exactly that and it worked for me.

The status for Portainer shown in the OMV webinterface should then change from "Created" to "Up [...]".

Dont need here.

Install updates -> KO Portainer -> Install apparmor -> Restart docker -> All ok.

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

Confirm! This helps for me! Thank you< good man=)


UPD:As a result, I decided to upgrade and still take the advice of ryecoaaron. In the end, I did everything, rebooted - everything works fine! Thanks!

Quote from nisitiiapi

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.

Display More

Works for me. Simple but effective solution on my armbian (32-bit) Helios4.

Manually installed apparmor/apparmor-utils to get around this issue. I install Docker using OMV but not Portainer as I install the portainer_agent manually to manage my containers from another server. Have recreated my containers and all seem to be working as expected.

Going forwards, despite the effort involved, it would seem sensible to have OMV accomodate apparmor where appropriate.

As some people have removed apparmor while others have taken the plunge there now exists two distinct groups that can 'test' OMV and identify any further operational issues over the coming weeks. Hopefully this might then enable those on who the rest of us depend, such as ryecoaaron to make best use of their valuable time. How can the results of such testing best be collated?