"Something went wrong trying to pull and start portainer"

1st Official Post

    I'm trying to set up Docker for the first time, following the guide. When I get to installing Portainer (step 4), it fails however with this message:



    I found an old thread with the same message, but nothing there seems to apply:

    - My DNS is working fine (indicated above and confirmed with ping from cli).

    - I'd never installed/used Docker before on this machine, nothing else is using port 8000.


    I've tried removing/reinstalling/restarting both Docker and Portainer, no luck. Ideas?

    Uninstalling Docker+Portainer from the OMV UI, but then also deleting and recreating the entire Docker folder before reinstalling seems to have worked. This time the Portainer installation did work.

  • arjan

    Added the Label resolved

    When you say you 'deleted and recreated the entire Docker folder', which Docker folder specifically are you talking about?


    I'm running into this same issue!


    I installed some updates through the GUI and then Docker and Portainer stopped working. I tried updating from 5.6 to 6.x - that did not resolve the issue. I've hit 'Remove' and 'Install' on both Docker and Portainer through the GUI with no success.


    I really don't want to delete the Docker directory if it will stop my portainer images from coming back up (Duplicati, etc.) as those took a long time to configure!

    I'm having the exact same issue as well - started after a power outage the last few days. I assume at this point I lost all my dockers and configuration which I'll get over but I just want to be able to get things back up and running again given all my drives/shares are still working great.

    • Official Post
    Quote from AustinML

    I'm having the exact same issue as well - started after a power outage the last few days. I assume at this point I lost all my dockers and configuration which I'll get over but I just want to be able to get things back up and running again given all my drives/shares are still working great.

    It is an apparmor issue because of change in docker. I pinned the thread hoping people would find it. You haven't lost anything.

    Thread
    docker not working since omv-upgrade
    i got this error in docker status but no container running in 2 OMV after upgrade docker docker-cli and pve-firmware

    (Code, 14 lines)

    in a second NAS i got same error then i tried to install apparmor and then containers run but then fail with error in permission denied when trying to bind a TPC socket port
    spupuz

    omv 6.4.2-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.7.16 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 2 Like 1
    • Official Post
    Quote from AustinML

    Still can't get Portainer running but so happy my dockers are all running again.

    Remove it and re-install it (assuming you used omv-extras to install it first).

    omv 6.4.2-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.7.16 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from AustinML

    Actually I found this in another thread:

    apt install apparmor apparmor-utils auditd

    which seems to fix everything. So glad all my stuff is still there!

    It is in the thread I linked to as well. That is the more dangerous solution and auditd is definitely not needed. Please read the thread I linked to.

    omv 6.4.2-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.7.16 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Quote from ryecoaaron

    It is in the thread I linked to as well. That is the more dangerous solution and auditd is definitely not needed. Please read the thread I linked to.

    Why is it dangerous?

    I got this error yesterday myself, but up until tuesday it was working fine.

    • Official Post
    Quote from CryptKeeper

    Why is it dangerous?

    if apparmor is not configured correctly, it could start blocking many things like docker and other services.

    omv 6.4.2-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.7.16 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1
    Quote from ryecoaaron

    It is an apparmor issue because of change in docker. I pinned the thread hoping people would find it. You haven't lost anything.

    Thread
    docker not working since omv-upgrade
    i got this error in docker status but no container running in 2 OMV after upgrade docker docker-cli and pve-firmware

    (Code, 14 lines)

    in a second NAS i got same error then i tried to install apparmor and then containers run but then fail with error in permission denied when trying to bind a TPC socket port
    spupuz

    This post links to the right thread to resolve this issue appropriately. Thank You

Participate now!

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

Register Yourself Login