Problems with Portainer

1. offizieller Beitrag

    During installation of Portainer it says :


    Docker storage :: /var/lib/docker

    Agent port:: 8000

    Web port:: 9000

    Yacht port:: 8001

    arch :: amd64

    option :: portainer

    state :: install

    extras :: 5.4.2

    DNS OK.

    No portainer containers or images to remove.

    Pulling and starting portainer/portainer-ce ...

    9ad9556846be8952a644cab6a78a8ca4602ad514a4df23e1c08ea177f0dad683

    Something went wrong trying to pull and start portainer ...

    Done.


    Under Portainer status it says created but if I try to open portainer it says connection refused.


    For Cockpit it says its installed but when I go to open yacht it says ERR_CONNECTION_REFUSED

    • Offizieller Beitrag
    Zitat von thegameksk

    Something went wrong trying to pull and start portainer ...

    Done.


    Under Portainer status it says created but if I try to open portainer it says connection refused.

    If it couldn't pull and start portainer, then the web interface will not work. Guessing there is something on your network blocking the image download. You will have to try pulling the image from the command line to get more info.

    Zitat von thegameksk

    For Cockpit it says its installed but when I go to open yacht it says ERR_CONNECTION_REFUSED

    Cockpit is not yacht. yacht is a portainer-alternative. cockpit is a server management web interface for kvm, docker, and more.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

    Zitat von ryecoaaron

    If it couldn't pull and start portainer, then the web interface will not work. Guessing there is something on your network blocking the image download. You will have to try pulling the image from the command line to get more info.

    Cockpit is not yacht. yacht is a portainer-alternative. cockpit is a server management web interface for kvm, docker, and more.


    Zitat von ryecoaaron

    If it couldn't pull and start portainer, then the web interface will not work. Guessing there is something on your network blocking the image download. You will have to try pulling the image from the command line to get more info.

    Cockpit is not yacht. yacht is a portainer-alternative. cockpit is a server management web interface for kvm, docker, and more.


    I made a mistake. Meant to put cockpit not yacht. Yacht and Cockpit are now both working after rebooting. I still have the same issue with Portainer. How would I go about pulling the image from command line>

  • thegameksk

    Hat den Titel des Themas von „Problems with Portainer and cockpit“ zu „Problems with Portainer“ geändert.
    • Offizieller Beitrag
    Zitat von thegameksk

    How would I go about pulling the image from command line>

    docker pull portainer/portainer-ce:latest

    • Offizieller Beitrag
    Zitat von thegameksk

    How do I get it open?

    That just pulls the image but does not start the container. Try the install portainer button again.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

    Zitat von ryecoaaron

    That just pulls the image but does not start the container. Try the install portainer button again.

    Docker storage :: /var/lib/docker

    Agent port:: 8000

    Web port:: 9000

    Yacht port:: 8001

    arch :: amd64

    option :: portainer

    state :: install

    extras :: 5.4.2

    DNS OK.

    Removing portainer/portainer-ce image ...

    Untagged: portainer/portainer-ce:latest

    Untagged: portainer/portainer-ce@sha256:0ab9d25e9ac7b663a51afc6853875b2055d8812fcaf677d0013eba32d0bf0e0d

    Deleted: sha256:a0a227bf03ddc8b88bbb74b1b84a8a7220c8fa95b122cbde2a7444f32dc30659

    Deleted: sha256:5d8ccdb2e9be5d114307c980f04f6b9d9b8d7f6ebbb7a7c323d76525408e31eb

    Deleted: sha256:dd4969f97241b9aefe2a70f560ce399ee9fa0354301c9aef841082ad52161ec5

    Pulling and starting portainer/portainer-ce ...

    2897b9178fc330a73a74ad3406489534fbb2eb3a33e1e1a729b3905e86024663

    Something went wrong trying to pull and start portainer ...

    Done

    • Offizieller Beitrag

    What about:


    docker run --name "portainer" -p 9000:9000 -p 8000:8000 --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

    • Offizieller Beitrag

    Some other container or service on your system is using port 8000. You need to fix that or change the port in the advanced settings of portainer.

    Zitat von francis

    I have the same problem, but I have no other container running on port 9000. What was your solution?

    Portainer uses two ports, 9000 and 8000. Did you check both?

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

    Hello,

    I am getting the same problem when trying to install Portainer over the Web-UI.

    I am running OMV 5 on Debian 10.

    There are no services running on either port 8000 and 9000. (netstat -tunlp)

    This is my output:

    I tried removing Portainer in the Web-UI and pulling the Image with docker pull portainer/portainer-ce:latest but this didnt change anything sadly.


    Then i removed Portainer again, ran

    docker run --name "portainer" -p 9000:9000 -p 8000:8000 --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest , it loaded the latest image and i got following error:



    Edit: I ran iptables -t filter -N DOCKER and service docker restart

    That fixed my problem.

    Einmal editiert, zuletzt von drumfort43 () aus folgendem Grund: Found solution i guess

    Danke 1

    Hi，


    I have the similar issue,

    When I isntall OMV 5 on Debian10, and using pve-kernel. the docker can't be used.

    Docker can be installed, but when I run a container, I will get error "listen tcp xxxx(port) socket permission denied."


    It still makes me confused.

    • Offizieller Beitrag
    Zitat von kelinjone

    hi

    I have the exact same pb as you, ERR_CONNECTION_REFUSED error, did anyone get the answer?

    Is your OMV installation recent? If so, check out this thread.

    Beitrag
    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):
    (Quelltext, 4 Zeilen)

    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

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden