Can't install/initiate Portainer on OMV5 / RPi 4

    • OMV 5.x (beta)
    • Resolved
    • Can't install/initiate Portainer on OMV5 / RPi 4

      Hi. I have OMV Extras v5.1.1, wich shows Docker as installed. When i try do install Portainer (by pressing the "Install Portainer" button), nothing happens. I only see the following dialog window:

      "option :: portainer
      state :: install
      No portainer containers or images to remove.
      Done."

      However, when I press the "Open Portainer web interface" button, it opens a tab on the browser with a "connection refused" result. I can't access Portainer. It would be nice to have a clue about what I coulf be doing wrong. Thanks!
    • This is a common problem.
      You can see it here:

      The best way is to install it manually.
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Just for info.
      The last hour I did a brand new installation of OMV v5 (over Debian 10). With latest OMV5-extras I've installed docker and tried to install Portainer, but I didn't have access to the web interface. Even OMV showed me that Portainer was successful installed.
      Than I've tried cockpit and this worked perfect. I could open the Webinterface of cockpit.
      So the best way right now to use Portainer is to install it by hand (via command line)

      Edit: sorry, but even installing Portainer by hand didn't work. I don't know what's going on here
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • heinsenberh82 wrote:

      Hi. I have OMV Extras v5.1.1, wich shows Docker as installed. When i try do install Portainer (by pressing the "Install Portainer" button), nothing happens. I only see the following dialog window:

      "option :: portainer
      state :: install
      No portainer containers or images to remove.
      Done."
      After installation of docker the network interface is broken and DNS does not work.

      Use omv-firstaid to reconfigure the network interface. After that installation of Portainer worked for me.
      Odroid HC2 - armbian - OMV4.x | Asrock Q1900DC-ITX - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • Thanks for your help guys.

      Reconfiguring the network interface through omv-firstaid didn't help me. Then I tried to install Portainer manually:

      Source Code

      1. docker pull portainer/portainer
      2. docker volume create portainer_data
      3. docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
      However, after the last command I got this message:
      docker: Error response from daemon: layer does not exist. See 'docker run --help'.

      Is there something else I could check?
    • Don't know if it makes a difference.From:portainer.readthedocs.io/en/latest/deployment.htmldocker run -d -p 9000:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
      Odroid HC2 - armbian - OMV4.x | Asrock Q1900DC-ITX - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • heinsenberg82 wrote:

      Thanks for the input man. I had already tried that, and just tried again, but no luck.
      All your errors point to the same problem I was having except for the error output in your post 5, you could search for the error via google, or uninstall docker run an apt clean, then apt autoremove from the cli, then reinstall docker.
      Raid is not a backup! Would you go skydiving without a parachute?
    • With the command


      Source Code

      1. omv-firstaid
      I could fix the problem with the connection to the internet.
      But apt-clean didn't help. I've no access to the webinterface of Portainer. I've tried to install via OMV-GUI and also by hand. No connection to Portainer.
      The installation of Portainer didn't give any errors.
      So no clue what's going on.
      Cockpit runs fine.
      Really funny...
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Thanks, this is the message I get, when I run the command:

      docker run portainer


      Source Code

      1. root@OMV-Testsystem:/var/lib/docker/containers/46f8790ddbbf8aff3188b9b7c286d9a6bd1351a5a984bb9787203e0fd82a7eab# service docker restart
      2. root@OMV-Testsystem:/var/lib/docker/containers/46f8790ddbbf8aff3188b9b7c286d9a6bd1351a5a984bb9787203e0fd82a7eab# docker run portainer
      3. Unable to find image 'portainer:latest' locally
      4. docker: Error response from daemon: pull access denied for portainer, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
      5. See 'docker run --help'.
      6. root@OMV-Testsystem:/var/lib/docker/containers/46f8790ddbbf8aff3188b9b7c286d9a6bd1351a5a984bb9787203e0fd82a7eab#
      Attached I've the log of the portainer-container. Maybe someone knows what's going on. I've installed Portainer described here
      Files
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • This is the output:

      Source Code

      1. root@OMV-Testsystem:/var/lib/docker/containers/46f8790ddbbf8aff3188b9b7c286d9a6bd1351a5a984bb9787203e0fd82a7eab# docker container ls
      2. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
      3. 46f8790ddbbf portainer/portainer "/portainer" 22 minutes ago Restarting (1) 30 seconds ago portainer
      The status seems very wired to me. Because I didn't do anything the last 5 minutes (watching football right now)
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2

      The post was edited 1 time, last by Huberer ().

    • My previous post was subjected to moderation (i don't know why), so let me try again.

      OK, this is what I did now.

      First, i ran service docker restart and BAM!, Portainer started! When I rebooted the machine, though, Portainer was not initialized. It only starts if i restart Docker service.

      Then I uninstalled Portainer, uninstalled Docker, ran an apt clean (through GUI), then an sudo apt-get autoremove (through bash). Btw, sudo apt-get autoremove didn't remove anynthing.

      Now, I can't even install Docker through OMV Extras GUI. The error appears to be similar with the error I got when tried to install Cockpit. Here's the full log:

      Source Code

      1. >>> *************** Error ***************
      2. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-installdocker docker install': option :: docker
      3. state :: install
      4. Docker storage :: /sharedfolders/docker
      5. Get:1 file:/var/cache/openmediavault/archives InRelease
      6. Ign:1 file:/var/cache/openmediavault/archives InRelease
      7. ...
      8. Get:4 file:/var/cache/openmediavault/archives Translation-en
      9. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      10. Hit:5 http://linux.teamviewer.com/deb stable InRelease
      11. Get:6 http://security.debian.org/debian-security buster/updates InRelease [39.1 kB]
      12. Hit:7 https://download.docker.com/linux/debian buster InRelease
      13. Hit:8 https://openmediavault.github.io/packages usul InRelease
      14. Hit:10 http://archive.raspberrypi.org/debian buster InRelease
      15. Get:9 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease [46.7 kB]
      16. Hit:11 http://packages.openmediavault.org/public usul InRelease
      17. Err:6 http://security.debian.org/debian-security buster/updates InRelease
      18. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50 NO_PUBKEY 112695A0E562B32A
      19. Ign:12 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease
      20. Ign:13 https://dl.bintray.com/openmediavault-plugin-developers/usul-testing buster InRelease
      21. ...
      22. Err:9 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease
      23. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
      24. Reading package lists...
      25. Failed to update apt repos.
      26. <<< *************************************
      27. >>> *************** Error ***************
      28. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-installdocker docker install': option :: docker
      29. state :: install
      30. Docker storage :: /sharedfolders/docker
      31. Get:1 file:/var/cache/openmediavault/archives InRelease
      32. Ign:1 file:/var/cache/openmediavault/archives InRelease
      33. Get:2 file:/var/cache/openmediavault/archives Release
      34. ...
      35. Get:3 file:/var/cache/openmediavault/archives Packages
      36. Get:4 file:/var/cache/openmediavault/archives Translation-en
      37. Ign:4 file:/var/cache/openmediavault/archives Translation-en
      38. Hit:5 http://linux.teamviewer.com/deb stable InRelease
      39. Get:6 http://security.debian.org/debian-security buster/updates InRelease [39.1 kB]
      40. Hit:7 https://download.docker.com/linux/debian buster InRelease
      41. Hit:8 https://openmediavault.github.io/packages usul InRelease
      42. Hit:10 http://archive.raspberrypi.org/debian buster InRelease
      43. Get:9 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease [46.7 kB]
      44. Hit:11 http://packages.openmediavault.org/public usul InRelease
      45. Err:6 http://security.debian.org/debian-security buster/updates InRelease
      46. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50 NO_PUBKEY 112695A0E562B32A
      47. Ign:12 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease
      48. Ign:13 https://dl.bintray.com/openmediavault-plugin-developers/usul-testing buster InRelease
      49. Get:14 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
      50. Ign:15 https://dl.bintray.com/openmediavault-plugin-developers/usul-extras buster InRelease
      51. Get:16 https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release [4363 B]
      52. Get:17 https://dl.bintray.com/openmediavault-plugin-developers/usul-testing buster Release [3538 B]
      53. Get:18 https://dl.bintray.com/openmediavault-plugin-developers/usul-extras buster Release [3538 B]
      54. Err:9 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease
      55. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
      56. Reading package lists...
      57. Failed to update apt repos.
      58. <<< *************************************
      Display All