Docker fails to install on clean OMV installation

    Following my last problem, I wiped my server installation. So the microsd card my server runs on has been formatted and freshly burned with my my iso Armbian_22.02.2_Helios4_bullseye_current_5.15.26.img.xz. And this OS has worked before on my server. Installing and updating took a while. But now OMV6 is now running from scratch.


    Before installing docker, the only tweak I made was to change docker's storage location to /srv/dev-disk-by-uuid-longnumberf/S/appdata/docker.

    Then I clicked install. This is where problems started.


    After waiting for the installer to do its magic, I got this ephemeral error message.




    I don't know what this means.


    The notification menu let me copy this massive error log to my clipboard.


    This is actually my second clean installation of OMV6 attempting to install docker. I got an error both times.

    So if anyone can help me get docker installed, I would really appreciate it. If it takes another clean installation of OMV6, I can do that. I'm getting pretty good at it.

    Post
    RE: docker not working since omv-upgrade
    *** This is for amd64 and i386 only ***
    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, 4 lines)

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

    If you have portainer and/or yacht installed, they will most likely need to be remove and reinstalled. You will not lose settings if this is done with omv-extras.
    ryecoaaron
    Quote from raulfg3
    Post
    RE: docker not working since omv-upgrade
    *** This is for amd64 and i386 only ***
    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, 4 lines)

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

    If you have portainer and/or yacht installed, they will most likely need to be remove and reinstalled. You will not lose settings if this is done with omv-extras.
    ryecoaaron

    The OP's hardware is not amd64/Intel.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Quote from raulfg3
    Post
    RE: docker not working since omv-upgrade
    *** This is for amd64 and i386 only ***
    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, 4 lines)

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

    If you have portainer and/or yacht installed, they will most likely need to be remove and reinstalled. You will not lose settings if this is done with omv-extras.
    ryecoaaron

    I saw that, but I assumed it wasn't relevant to me because I'm using a clean install. I don't even know what apparmor is. So I've never gone out of my way to install it.

    Quote from HyronHelper

    I saw that, but I assumed it wasn't relevant to me because I'm using a clean install. I don't even know what apparmor is. So I've never gone out of my way to install it.

    The information you provided says your hardware is ARM, so that fix cannot work for you.


    Try the fix in this post:


    Post
    RE: docker not working since omv-upgrade
    […]

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

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Quote from gderf

    The information you provided says your hardware is ARM, so that fix cannot work for you.


    Try the fix in this post:


    Post
    RE: docker not working since omv-upgrade
    […]

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

    I used WinSCP, editted /boot/armbianEnv.txt

    Inside the file I added extraargs=apparmor=0 to the end of the file.


    After opening OMV again, it claimed docker was installed. Reinstalling docker produced no error. But then the server prompted me to restart to apply changes. I did that. And now over and hour has gone by and I still can't log into the server.


    Forcing the server to restart again leads me to the same place. I can no longer access OMV with my browser. I cannot access my server through SSH anymore. It's just completely unresponsive now.

Participate now!

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

Register Yourself Login