docker not working since omv-upgrade

Zitat von ryecoaaron

There is nothing OMV that is not accommodating apparmor. docker is the only thing I have found and that is not OMV. omv-extras can install it but it still isn't part of OMV.

So, this is the best desicion?

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

It works for me, so Can I exhale and continue to work calmly with my OMV?

Zitat von ryecoaaron

I think it is. OMV has not been using apparmor. This just disables at the OS level since docker thinks it is enabled because apparmor-utils is not installed. Installing apparmor-utils will install apparmor which can cause issue (not saying apparmor is bad - I use it on Ubuntu).

Yes

Thx! You're the best!=)

Zitat von 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.

Alles anzeigen

It works for Odroid HC-2 (armbian, ODROID-XU4 platform).

But I had to create not exist file armbianEnv.txt (/boot/armbianEnv.txt)

Thank you

On my baremetal OMV6 (x86), the docker does not start and samba (smbd) crash with a segfault.

Installing apparmor-utils does not solve the problem but disable apparmor works fine.

Thank you for the solution.

That works for me:

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

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

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

apt-get install apparmor-utils

I have read it. For me it works. But it is strange that for some systems it works and for other not. Is disabling AppArmor the safest way to get Portainer working again?

Zitat von 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

Thank you, thats solve my problem! after that install portainer on gui thats all..

Zitat von pgk831

Thank you, thats solve my problem! after that install portainer on gui thats all..

That workaround solved for me.

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

Tried also this workaround, but with no luck

I am starting a fresh install on my media server; heavily dependent on Docker. Would it make sense to apply this fix now prior to installing Docker?

Zitat von 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

I am stuck with no portainer, question if I just use OMV6 without omv-extras what am I losing. Will I still have

access to the miniDLNA pluggin, file browser or KMV or do these rely on docker?

I was freaking out yesterday after the update to docker when all my dockers and portainer all of a sudden stopped working. I reverted back to the previous versions of docker as a temporary fix. After reading all the posts in this thread, is this the recommended "workaround"?

apt-get install apparmor-utils

Then

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

To disable apparmor for the time being?

Am I missing any steps or should this be good for now?

Thank you everyone for your assistance in getting to the bottom of this strange issue.

Zitat von 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

I eventually found my way here because of the same problem. I ran that command in Putty which got my Plex and qBittorrent to work again. However I can no longer go to the OMVExtras page when logged into my server's GUI. It says Software Failure. Do I now have to re-install omv-extras somehow?

RUsum1 no you don't have to

I had the same issue. Uninstalling worked for me

Zitat von 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 a lot. Worked for me also
You saved my day