no connection to Portainer after installation of docker under OMV v5

    • OMV 5.x (beta)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Thanks for the info. Maybe it has something to do with the activated tab for the installation of Portainer after enabling omv-extras.
      Because when you have a look on this side you can see the enabled Portainer docker (it's in green) even you haven't installed docker. Maybe this is the issue?
      And after installation of docker the system won't install portainer.

      I had the same issue. By installing portainer manually (via CLI) it was working like it should
      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 Buster(always up-to-date), OMV v5 (always latest), Proxmox-Kernel, omv-extras-plugin (always latests), AutoShutdown-Plugin, Docker with PlexMediaServer, TVHeadendServer (unstable release)

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

      Source Code

      1. apt-cache policy cockpit
      2. cockpit:
      3. Installed: (none)
      4. Candidate: 202.1-1~bpo10+1
      5. Version table:
      6. 202.1-1~bpo10+1 500
      7. 100 http://httpredir.debian.org/debian buster-backports/main amd64 Packages
      8. 188-1 500
      9. 500 http://deb.debian.org/debian buster/main amd64 Packages
      that is after enabling cockpit and savein OMV-Extras, dpkg --list does not display cockpit.

      I am now tempted to just reinstall and try again, thankfully this is just testing :)
      Raid is not a backup! Would you go skydiving without a parachute?
    • Sorted!! Clean install, made the relevant changes under system, wiped the hard drive and created a file system, ssh into server and ran wget -O - http://omv-extras.org/install | bash this installs OMV-Extras, from plugins installed flash memory.

      Back to OMV-Extras enabled Extras repo -> Save don't know if this is necessary but did it anyway. Updates -> apt clean.

      Created a share for Docker Storage on the hard drive -> Save
      Disabled Install Portainer -> Save
      Install Docker :thumbup:
      Updates -> apt clean (I do this a lot if I'm having problems)
      Enable Install Portainer -> Save
      Install Docker this will go through the process of the install but a message comes back 0 Installed 0 Upgraded + another, but the fundamental part portainer_data which outputs the seriously long container reference
      Open Portainer web interface :thumbsup: :thumbsup: success

      Went through the same process for Cockpit
      Open Cockpit web interface :thumbsup: :thumbsup: success

      Having a quick look at Cockpit -> Create VM I still can't find how you would point the install to a share on the server, this has come up on the forum. OK further investigation one option is missing in the Cockpit install, storage, and the issue of creating the VM on a share on your server is not possible, this was asked about here the relevance of that is your VM is going to be installed on your boot device!!

      I have added the storage option from the cli, but even though I have installed that you cannot specify where to install the VM. Does this have something to do with the output from apt-cache referencing 188.
      Raid is not a backup! Would you go skydiving without a parachute?
    • @geaves

      I followed your guide, but I used the script to install OMV + omv-extras directly. Did a clean installation on VMware Fusion.

      It didn't work either. So no connection to portainer ;(
      But I can install it manually anyway. And when I get a second PC I will install it on a real hardware.
      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 Buster(always up-to-date), OMV v5 (always latest), Proxmox-Kernel, omv-extras-plugin (always latests), AutoShutdown-Plugin, Docker with PlexMediaServer, TVHeadendServer (unstable release)

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


      I've also created a new script that will install OMV itself if it isn't installed already - github.com/OpenMediaVault-Plugin-Developers/installScript

      Yesterday and today I did a new installation of Debian 10 (netinstall - just ssh server and system utilities enabled) and used your script to install OMV over Debian 10.
      Unfortunately the script stops because of missing sudo.
      I normally install Debian, login with root (direct on the server), enable ssh and when I connect via a client to the server (with 'ssh root@IP-server') and try to run the script, it says that sudo is missing.
      So I've installed sudo by hand and afterwards everything is working fine.

      Maybe you can update in your script the matter to install sudo first.

      Thanks in advance
      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 Buster(always up-to-date), OMV v5 (always latest), Proxmox-Kernel, omv-extras-plugin (always latests), AutoShutdown-Plugin, Docker with PlexMediaServer, TVHeadendServer (unstable release)

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

      Unfortunately the script stops because of missing sudo.
      ...
      Maybe you can update in your script the matter to install sudo first.
      I want the script to be executable using sudo though. I added the prerequisites to install to the README - github.com/OpenMediaVault-Plug…ipt/blob/master/README.md
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • New Problem. I did some updated today and after restarting my server all docker containers were gone. I tried apt clean and pressed "install docker" again. After that my docker containers returned. Only portainer stays down. Also I cant manually start portainer because of this error message docker: Error response from daemon: network bridge is ambiguous (2 matches found on name).
      docker network ls gives:

      Source Code

      1. NETWORK ID NAME DRIVER SCOPE
      2. 0cef225c0710 bridge bridge local
      3. 4207ded0bc05 bridge bridge local
      4. f75e7ccbde17 host host local
      5. 4d79b7421042 host host local
      6. 4446a2322aa1 my-net bridge local
      7. cdee325e3d22 none null local
      8. 3a9302b91d49 resiliosync_default bridge local
      9. 2c219cda2b0f workgroup macvlan local
      when I try docker network rm bride then I get Error response from daemon: bridge is a pre-defined network and cannot be removed

      Any ideas?
    • Morlan wrote:

      Any ideas?
      Docker probably started before your storage. There a couple of threads with ideas about that. portainer is set to restart on boot unless stopped and just uses the default network. You have a lot of networks. So, hard to say what happened.
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Morlan wrote:

      I thinks its the duplication of the bridge and host networks that causes the problems. Dont know how that happened.
      Good point. I didn't notice that. Maybe caused by docker-compose?
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!