docker not working since omv-upgrade

Thanks.

I have SYS_PTRACE enabled in netdata and no journal entries since Friday.

root@omv:/var/log/journal/78a0747a30104ea9a04aedab22a30f62# journalctl --since=yesterday
-- Journal begins at Sun 2022-05-08 14:55:37 AEST, ends at Fri 2023-02-03 13:14:45 AEDT. --
-- No entries --
root@omv:/var/log/journal/78a0747a30104ea9a04aedab22a30f62#

Quote from gregeeh

I have SYS_PTRACE enabled in netdata and no journal entries since Friday.

Code

root@omv:/var/log/journal/78a0747a30104ea9a04aedab22a30f62# journalctl --since=yesterday
-- Journal begins at Sun 2022-05-08 14:55:37 AEST, ends at Fri 2023-02-03 13:14:45 AEDT. --
-- No entries --
root@omv:/var/log/journal/78a0747a30104ea9a04aedab22a30f62#

If you have apparmor disabled you will not see any ptrace journal entries from netdata.

Quote from gderf

If you have apparmor disabled you will not see any ptrace journal entries from netdata.

That explains it, thanks.

Ok i enableb apparmor and docker is working again. Only one strange error remains. After booting portainer will only find the inveronment with de portainer install. If i the restart docker again it will find the envronment wilth all my cotainers installed. And i will still only show 1 envoronment.

It looks as if portainer is up and running before my file system is up.

Is it possible to make a summary of the problem and the various solutions? I find it very difficult to determine the correct sollution for me. From what i read there are 2 possibillties:

1. Completely disable apparmor in your OS

2. install apparmor on OMV and configure it.

The one or the other seems to be dependant on logging, but what and how is beyond my limited experience.

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 ryecoaaron.

I too ran into trouble after the update. Your solution got me back up and running.

Hello, is this solution definitely for Armbian???

Add extraargs=apparmor=0 to ArmbianEnv.txt

Because I've already run the script from ryecoaaron, I'm afraid that my nano pi won't boot anymore

Armbian hat doch kein Grub

Guys iam new to the whole thingy. My portainer also doesn't work anymore, how do i fix it? Seems that it not listen at port 9000 anymore? My installation of PLEX inside portainer does work. I dont get it...Restart, reinstall etc. doens't help.

ty

Read the firt page...

Ty does work now fixed it with

apt-get install apparmor-utils && apt install -f
sudo docker restart portainer

Quote from Aux

Hello, is this solution definitely for Armbian???

Add extraargs=apparmor=0 to ArmbianEnv.txt

Because I've already run the script from ryecoaaron, I'm afraid that my nano pi won't boot anymore

Armbian hat doch kein Grub

Display More

Worked for my RockPro64 running Armbian. No other changes needed.

So I saw a bunch of people having issues with this and have held off updating anything in OMV. Has this been addressed? Am I able to simply update in the webGUI and be fine? Or should I continue to hold off for some proper fix? I am trying to avoid running anything in terminal, unless you're telling me that's the only way to fix it and move forward...

This has been solved and the solutions have been repeatedly posted to the forum. Have you read any of those posts? You will have apply the fix in the terminal.

If you don't have any problems, you don't have to do anything.

A massive shout out to this amazing community. I updated my OMV this morning (Australia) and started to freak out when it went pear shaped. Copied the error message, found this thread and was back up and running in under 10 minutes! Love to you all from Down Under

Quote from gderf

This has been solved and the solutions have been repeatedly posted to the forum. Have you read any of those posts? You will have apply the fix in the terminal.

I read the solutions as workarounds and thought that OMV updater would be pushing out some fix. I guess lucky for me I know it will throw errors once I update and can refer to fixes immediately from this thread. I was thinking of people who may not know and will just hit update blindly...

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

Didn't work for me. I used armbian-config's "edit boot-enviroment", added "xextraargs=apparmor=0" and after a reboot I still get:

docker start portainer
Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output:
error: exec: "apparmor_parser": executable file not found in $PATH
Error: failed to start containers: portainer

Quote from tordenflesk

added "xextraargs=apparmor=0" and after a reboot I still get

It's extraargs=, not xextraargs=

Worked for me. I edited /boot/armbianEnv.txt directly.

Quote from Aux

Add extraargs=apparmor=0 to ArmbianEnv.txt

It's /boot/armbianEnv.txt, not ArmbianEnv.txt