Docker CE - repo enabled but Failed to fetch https://dl.bin...

    • OMV 3.x

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

    • Docker CE - repo enabled but Failed to fetch https://dl.bin...

      Hi all,

      I have a RPi and wanted to use docker. I enabled the Docker CE repo but when I try to install the plug-in or update anything I get the following error.

      W: Failed to fetch dl.bintray.com/openmediavault-…cker/dists/jessie/Release Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead.

      I have tried disabling the repo. restart. reenable etc but I keep getting the error as soon as I enable the repo.

      Any ideas?

      Thanks.
    • jata1 wrote:

      what about docker on a rock64? Same situation as RPi?
      rock64 is the same architecture - arm. I would use amd64.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Hi Guys
      New to the Forum and OMV on the raspberrypi,

      did all the extra updates , so i could install sonarr, radarr deluge, transmissionbt, plex,

      how ever docker CE shows up in the repos and when i enable it, i dont get any plug ins, is it correct that it is not supported on the PI

      or is any docker version supported ,

      as would like to add Jacket to help add some more indexes in sonarr/radarr

      new to all this stuff

      thanks
      OMV 3.0.98 RPi 3 OMV 4.0.14 amd.64
    • You can manually install docker on raspberry pi and not use the omv plugin if you want.
      I'm a Docker Technical Sales Professional.

      1 NAS OMV 4 (Intel Pentium 4560 3.5 GHz, Asrock H110M-ITX, 24 Gb DDR4, 2*4 To Seagate Ironwolf Nas, 2*4 To WD red)
      1 RPI 3 seedbox with omv 3.X
      1 Backup Server omv 4 (core 2 quad q6600, 4 Gb DDR2, 2*4To WD blue)
    • Yes you can do a curl.
      Once installed, if you want to run an image you have to do it by command. If you want a GUI you can install portainer.
      I'm a Docker Technical Sales Professional.

      1 NAS OMV 4 (Intel Pentium 4560 3.5 GHz, Asrock H110M-ITX, 24 Gb DDR4, 2*4 To Seagate Ironwolf Nas, 2*4 To WD red)
      1 RPI 3 seedbox with omv 3.X
      1 Backup Server omv 4 (core 2 quad q6600, 4 Gb DDR2, 2*4To WD blue)
    • can i ask which is the latest docker ver
      curl -sSL get.docker.com | sh

      got this error
      E: Sub-process /usr/bin/dpkg returned an error code (1)


      install this followed this


      Hello from Docker on armhf!
      This message shows that your installation appears to be working correctly.

      To generate this message, Docker took the following steps:
      1. The Docker client contacted the Docker daemon.
      2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
      3. The Docker daemon created a new container from that image which runs the
      executable that produces the output you are currently reading.
      4. The Docker daemon streamed that output to the Docker client, which sent it
      to your terminal.


      root@raspberrypi:~# docker version
      Client:
      Version: 1.11.1
      API version: 1.23
      Go version: go1.4.3
      Git commit: 5604cbe
      Built: Mon May 9 00:50:14 2016
      OS/Arch: linux/arm

      Server:
      Version: 1.11.1
      API version: 1.23
      Go version: go1.4.3
      Git commit: 5604cbe
      Built: Mon May 9 00:50:14 2016
      so i'm i all good

      or is there a newer version
      sorry for the questions
      OMV 3.0.98 RPi 3 OMV 4.0.14 amd.64
    • If you have Docker plugin in omv please remove it. Try this command before installing Docker:

      Source Code

      1. sudo apt-get clean
      I'm a Docker Technical Sales Professional.

      1 NAS OMV 4 (Intel Pentium 4560 3.5 GHz, Asrock H110M-ITX, 24 Gb DDR4, 2*4 To Seagate Ironwolf Nas, 2*4 To WD red)
      1 RPI 3 seedbox with omv 3.X
      1 Backup Server omv 4 (core 2 quad q6600, 4 Gb DDR2, 2*4To WD blue)
    • hi
      started from scratch as

      installed manually via curl command
      got to portainer web ui and stuck on the Endpoint URL

      url or ip address of a Docker Host. the docker host API must be exposed over TCP port

      totally lost at this point, as all new to me

      what address do i add here----have searched but only just learning this stuff

      thanks
      OMV 3.0.98 RPi 3 OMV 4.0.14 amd.64

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

    • The IP is the IP of your OMV host (the same IP you use when you want to connect to omv GUI).
      The port is 2375 (by default).

      So your endpoint url is :

      omvHostIP:2375
      I'm a Docker Technical Sales Professional.

      1 NAS OMV 4 (Intel Pentium 4560 3.5 GHz, Asrock H110M-ITX, 24 Gb DDR4, 2*4 To Seagate Ironwolf Nas, 2*4 To WD red)
      1 RPI 3 seedbox with omv 3.X
      1 Backup Server omv 4 (core 2 quad q6600, 4 Gb DDR2, 2*4To WD blue)
    • tried to delcare an end point , not sure which ip address so tried both 172.17.0.1 and 192.168.0.39 with port 2375 not sure wha the errors mean

      docker run -d -p 9000:9000 portainer/portainer -H tcp://<REMOTE_HOST>:<REMOTE_PORT>


      root@raspberrypi:~# ifconfig
      docker0 Link encap:Ethernet HWaddr 02:42:8d:3c:53:9b
      inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:944 errors:0 dropped:0 overruns:0 frame:0
      TX packets:1150 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:72173 (70.4 KiB) TX bytes:200488 (195.7 KiB)

      eth0 Link encap:Ethernet HWaddr b8:27:eb:d6:8c:77
      inet addr:192.168.0.39 Bcast:192.168.0.255 Mask:255.255.255.0
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:100317 errors:0 dropped:0 overruns:0 frame:0
      TX packets:12396 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:11613705 (11.0 MiB) TX bytes:2304530 (2.1 MiB)

      root@raspberrypi:~# docker run -d -p 9000:9000 portainer/portainer -H tcp://192.168.0.39:2375
      d8b2422bdc4514110e14ceec8a17632c871ca0bb9fc8f89c313590bb90d3b2f2
      docker: Error response from daemon: driver failed programming external connectivity on endpoint laughing_mccarthy (55711986795eddd22b89b5cb88cbcbaa4cd6cf5a49af6883c7a43fbfba023d19): Bind for 0.0.0.0:9000 failed: port is already allocated.
      root@raspberrypi:~#




      root@raspberrypi:~# docker run -d -p 9000:9000 portainer/portainer -H tcp://172.17.0.1:2375
      6fc12081cdd1cce864c49c5731bb1ea95cd1f403265b16e721999470541e64f6
      docker: Error response from daemon: driver failed programming external connectivity on endpoint optimistic_clarke (20e8a0f96d68215dc96b40a519af58c9f37080a91aa654fbd292fdd52a0c1847): Bind for 0.0.0.0:9000 failed: port is already allocated.

      thanks
      OMV 3.0.98 RPi 3 OMV 4.0.14 amd.64
    • gdf wrote:

      Bind for 0.0.0.0:9000 failed: port is already allocated.
      You have this error because something (portainer) is already using this port. You launch the docker run command so port 9000 is in use when you relauch. When it happens you have 2 choices:
      1. Delete container using this port (not a solution in a real case but in your case, you must delete your running portainer container).
      2. Use another port in port binding (for example: -p 9001:9000 instead of -p 9000:9000)


      In your case:

      Source Code

      1. docker ps


      You will get something like:

      Source Code

      1. $ docker ps
      2. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
      3. 4935a08f0d8f portainer/portainer "/portainer" 4 weeks ago Up 6 days 0.0.0.0:9000->9000/tcp affectionate_jones
      Stop and Delete this container:

      Source Code

      1. docker stop containerIDorName
      2. docker rm containerIDorName

      Now:

      Source Code

      1. docker run -d -p 9000:9000 --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /opt/portainer:/data portainer/portainer -H unix:///var/run/docker.sock
      I'm a Docker Technical Sales Professional.

      1 NAS OMV 4 (Intel Pentium 4560 3.5 GHz, Asrock H110M-ITX, 24 Gb DDR4, 2*4 To Seagate Ironwolf Nas, 2*4 To WD red)
      1 RPI 3 seedbox with omv 3.X
      1 Backup Server omv 4 (core 2 quad q6600, 4 Gb DDR2, 2*4To WD blue)