Ok, I got the config to finally show in the external location and I can find the config and edit it...
Do i need to open to port in the docker also to allow the port to be passed from the system to the docker container?
Ok, I got the config to finally show in the external location and I can find the config and edit it...
Do i need to open to port in the docker also to allow the port to be passed from the system to the docker container?
nobody has an idea for my problem?
thank you in advance
I just don't get it... Qbittorent never needs me to open ports, Deluge doesn't need it either. One is running in a docker the other is not. rtorrent the port is ALWAYS closed.This means I get horrible throughput.
nobody has an idea for my problem?
thank you in advance
Have you followed the instructions of the error message? It might be wise to take that first step, and the potentially share the output.
I just don't get it... Qbittorent never needs me to open ports, Deluge doesn't need it either. One is running in a docker the other is not. rtorrent the port is ALWAYS closed.This means I get horrible throughput.
Based on this not being related to the topic of the Docker GUI plugin, I'd suggest opening a separate thread or even opening an issue with the Docker container creator/maintainer.
On the "never needs me to open ports" - It's not necessarily an issue of opening ports in Docker. If you can get connections and downloads to work at all, then it's the first issue of firewall/router ports. If the ports weren't open or functioning inside the docker container, you would get 0 connection. I'd suggest that perhaps the other apps are using a default port that is the same and already opened on your firewall/router, or are using UPnP to open the ports and the other is not. Lastly, make sure if you are "testing" that you are using the same exact torrent file in multiple apps to compare "horrible throughput". Every torrent is different and can't be compared independently or you will no-doubtedly see great variations in perceived performance.
Hi all,
I am a docker newbie and I am trying to get the OMV docker GUI plugin working on my rock64 board - OMV3 / linux / jessie / armhf
From the rock64 forum boards, I have read that some people have docker working so I think it is possible but it looks quite complicated (for me).
My OMV 3 setup is clean/new and up to date (apt-get update) and working well but I get the following error(s) when I try to add the docker CE repo and update.
W: Failed to fetch https://download.docker.com/li…an/dists/jessie/InRelease Unable to find expected entry 'stable/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)
W: Failed to fetch https://dl.bintray.com/openmed…cker/dists/jessie/Release Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)
Any ideas how I can resolve these errors? I'm running armhf (not arm64).
Thanks,
Looks like you will have to build docker to your arch. Docker doesn't supply arm64. Be careful after building to download images corresponding to your arch, not anything you find on the hub.
omv plugins are arch agnostic, but in this case originally it was restricted to amd64, since docker started distributing this arch originally. @ryecoaaron lifted the restriction to add armhf because docker now ships armhf.
Once you get docker build for your arch you can install the plugin manually
OK. Thanks. I sense this is going to be a challenging project for me. haha.
I will look into getting docker installed through the rock64 community and let you know how I get on.
I will look into getting docker installed through the rock64 community and let you know how I get on
I just purchased mine, i'll let you know also in a few weeks see how it goes.
first step (installing docker CE) was easier than I expected...
Used instructions here to install docker CE
https://docs.docker.com/engine…bian/#install-docker-ce-1
then tested by using
sudo docker run armhf/hello-world
latest: Pulling from armhf/hello-world
a0691bf12e4e: Pull complete
Digest: sha256:9701edc932223a66e49dd6c894a11db8c2cf4eccd1414f1ec105a623bf16b426
Status: Downloaded newer image for armhf/hello-world:latest
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.
@subzero79 - can you explain how i can install the plugin manually?
dpkg -i packagefilename.deb
You can get the plugin from Omvextras bintray repository.
do you mean here? I can't seem to find it (sorry if i'm being stupid)
https://bintray.com/openmediavault-plugin-developers/erasmus
Have you followed the instructions of the error message? It might be wise to take that first step, and the potentially share the output.
Hello,
Unfortunately I do not understand the error message.
Here are the actions and messages that OMV returns to me
root@NAS:~# apt-get install openmediavault-docker-gui
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets supplémentaires suivants seront installés :
docker-engine imagemagick-common liblqr-1-0 libmagickcore-6.q16-2
libmagickwand-6.q16-2 omvextras-common php-symfony-class-loader php5-curl
php5-imagick
Paquets suggérés :
libmagickcore-6.q16-2-extra
Paquets recommandés :
aufs-tools cgroupfs-mount cgroup-lite git ghostscript gsfonts
ttf-dejavu-core
Les NOUVEAUX paquets suivants seront installés :
docker-engine imagemagick-common liblqr-1-0 libmagickcore-6.q16-2
libmagickwand-6.q16-2 omvextras-common openmediavault-docker-gui
php-symfony-class-loader php5-curl php5-imagick
0 mis à jour, 10 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 21,7 Mo dans les archives.
Après cette opération, 102 Mo d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Réception de : 1 http://ftp.fr.debian.org/debian/ jessie/main liblqr-1-0 amd64 0.4.2-2 [24,6 kB]
Réception de : 2 http://security.debian.org/ jessie/updates/main imagemagick-common all 8:6.8.9.9-5+deb8u11 [153 kB]
Réception de : 3 http://ftp.fr.debian.org/debian/ jessie/main php-symfony-class-loader all 2.3.21+dfsg-4+deb8u3 [21,4 kB]
Réception de : 4 http://security.debian.org/ jessie/updates/main libmagickcore-6.q16-2 amd64 8:6.8.9.9-5+deb8u11 [1 695 kB]
Réception de : 5 http://ftp.fr.debian.org/debian/ jessie/main php5-curl amd64 5.6.30+dfsg-0+deb8u1 [28,0 kB]
Réception de : 6 https://dl.bintray.com/openmediavault-plugin-developers/erasmus/ jessie/main omvextras-common all 3.0.1 [6 628 B]
Réception de : 7 https://apt.dockerproject.org/repo/ debian-jessie/main docker-engine amd64 17.05.0~ce-0~debian-jessie [19,2 MB]
Réception de : 8 http://ftp.fr.debian.org/debian/ jessie/main php5-imagick amd64 3.2.0~rc1-1 [101 kB]
Réception de : 9 https://dl.bintray.com/openmediavault-plugin-developers/erasmus-docker/ jessie/main openmediavault-docker-gui amd64 3.1.9 [49,5 kB]
Réception de : 10 http://security.debian.org/ jessie/updates/main libmagickwand-6.q16-2 amd64 8:6.8.9.9-5+deb8u11 [407 kB]
72% [7 docker-engine 13,2 MB/19,2 MB 69%] 191 kB/s 31s 21,7 Mo réceptionnés en 1min 34s (229 ko/s)
Sélection du paquet imagemagick-common précédemment désélectionné.
(Lecture de la base de données... 96600 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../imagemagick-common_8%3a6.8.9.9-5+deb8u11_all.deb ...
Dépaquetage de imagemagick-common (8:6.8.9.9-5+deb8u11) ...
Sélection du paquet liblqr-1-0:amd64 précédemment désélectionné.
Préparation du dépaquetage de .../liblqr-1-0_0.4.2-2_amd64.deb ...
Dépaquetage de liblqr-1-0:amd64 (0.4.2-2) ...
Sélection du paquet libmagickcore-6.q16-2:amd64 précédemment désélectionné.
Préparation du dépaquetage de .../libmagickcore-6.q16-2_8%3a6.8.9.9-5+deb8u11_amd64.deb ...
Dépaquetage de libmagickcore-6.q16-2:amd64 (8:6.8.9.9-5+deb8u11) ...
Sélection du paquet libmagickwand-6.q16-2:amd64 précédemment désélectionné.
Préparation du dépaquetage de .../libmagickwand-6.q16-2_8%3a6.8.9.9-5+deb8u11_amd64.deb ...
Dépaquetage de libmagickwand-6.q16-2:amd64 (8:6.8.9.9-5+deb8u11) ...
Sélection du paquet docker-engine précédemment désélectionné.
Préparation du dépaquetage de .../docker-engine_17.05.0~ce-0~debian-jessie_amd64.deb ...
Dépaquetage de docker-engine (17.05.0~ce-0~debian-jessie) ...
Sélection du paquet php-symfony-class-loader précédemment désélectionné.
Préparation du dépaquetage de .../php-symfony-class-loader_2.3.21+dfsg-4+deb8u3_all.deb ...
Dépaquetage de php-symfony-class-loader (2.3.21+dfsg-4+deb8u3) ...
Sélection du paquet omvextras-common précédemment désélectionné.
Préparation du dépaquetage de .../omvextras-common_3.0.1_all.deb ...
Dépaquetage de omvextras-common (3.0.1) ...
Sélection du paquet php5-curl précédemment désélectionné.
Préparation du dépaquetage de .../php5-curl_5.6.30+dfsg-0+deb8u1_amd64.deb ...
Dépaquetage de php5-curl (5.6.30+dfsg-0+deb8u1) ...
Sélection du paquet php5-imagick précédemment désélectionné.
Préparation du dépaquetage de .../php5-imagick_3.2.0~rc1-1_amd64.deb ...
Dépaquetage de php5-imagick (3.2.0~rc1-1) ...
Sélection du paquet openmediavault-docker-gui précédemment désélectionné.
Préparation du dépaquetage de .../openmediavault-docker-gui_3.1.9_amd64.deb ...
Dépaquetage de openmediavault-docker-gui (3.1.9) ...
Traitement des actions différées (« triggers ») pour man-db (2.7.0.2-5) ...
Traitement des actions différées (« triggers ») pour systemd (215-17+deb8u7) ...
Traitement des actions différées (« triggers ») pour openmediavault (3.0.93) ...
Restarting engine daemon ...
Traitement des actions différées (« triggers ») pour php5-fpm (5.6.30+dfsg-0+deb8u1) ...
Paramétrage de imagemagick-common (8:6.8.9.9-5+deb8u11) ...
Paramétrage de liblqr-1-0:amd64 (0.4.2-2) ...
Paramétrage de libmagickcore-6.q16-2:amd64 (8:6.8.9.9-5+deb8u11) ...
Paramétrage de libmagickwand-6.q16-2:amd64 (8:6.8.9.9-5+deb8u11) ...
Paramétrage de docker-engine (17.05.0~ce-0~debian-jessie) ...
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: erreur de traitement du paquet docker-engine (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Paramétrage de php-symfony-class-loader (2.3.21+dfsg-4+deb8u3) ...
Paramétrage de omvextras-common (3.0.1) ...
Paramétrage de php5-curl (5.6.30+dfsg-0+deb8u1) ...
php5_invoke: Enable module curl for cgi SAPI
php5_invoke: Enable module curl for fpm SAPI
php5_invoke: Enable module curl for cli SAPI
Paramétrage de php5-imagick (3.2.0~rc1-1) ...
php5_invoke: Enable module imagick for cgi SAPI
php5_invoke: Enable module imagick for fpm SAPI
php5_invoke: Enable module imagick for cli SAPI
dpkg: des problèmes de dépendances empêchent la configuration de openmediavault-docker-gui :
openmediavault-docker-gui dépend de docker-engine (>= 1.12) ; cependant :
Le paquet docker-engine n'est pas encore configuré.
dpkg: erreur de traitement du paquet openmediavault-docker-gui (--configure) :
problèmes de dépendances - laissé non configuré
Traitement des actions différées (« triggers ») pour libc-bin (2.19-18+deb8u10) ...
Traitement des actions différées (« triggers ») pour openmediavault (3.0.93) ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Traitement des actions différées (« triggers ») pour php5-fpm (5.6.30+dfsg-0+deb8u1) ...
Des erreurs ont été rencontrées pendant l'exécution :
docker-engine
openmediavault-docker-gui
E: Sub-process /usr/bin/dpkg returned an error code (1)
Alles anzeigen
Hello All,
I am New to docker, I love the idea of containers.
I did get docker installed on my OMV 3.0.
I then tested it with
everything worked fine.
I am looking to install the plugin but it keeps failing.
Here is the install log.
>>> *************** Error ***************
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --allow-unauthenticated --reinstall install openmediavault-docker-gui 2>&1' with exit code '100': Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
openmediavault-docker-gui : Depends: php5-imagick but it is not installable
E
:
Unable to correct problems, you have held broken packages.
<<< *************************************
Alles anzeigen
Any Ideas ?
LOoks like you’re missing some Debian repos. How did you install Omv or Debian ?
Please post cat /etc/apt/sources.list
I just installed it from the ISO downloaded form openmediavault.org.
here is my sources.
cat /etc/apt/sources.list
#
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20170731-21:43]/ jessie contrib main non-free
#deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20170731-21:43]/ jessie contrib main non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.au.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.au.debian.org/debian/ jessie-updates main contrib non-free
root@openmediavault:~#
Alles anzeigen
you're missing some repos.
Add this line to the sources.list
deb http://deb.debian.org/debian/ jessie main contrib non-free
Hello guys,
today I updated the docker ce package to the latest version. Now I see the following notification, when I navigate to "Services - Docker" in the omv webui:
If I go to "Show details", I see the following Error description:
Error #0:
exception 'ImagickException' with message 'Imagick::__construct(): HTTP request failed! HTTP/1.1 404 Not Found
' in /usr/share/openmediavault/engined/rpc/docker.inc:1504
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/docker.inc(1504): Imagick->__construct('https://raw.git...')
#1 [internal function]: OMVRpcServiceDocker->syncDockerLogos(NULL, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('syncDockerLogos', NULL, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'syncDockerLogos', NULL, Array, 1)
#5 {main}
Next exception 'ImagickException' with message 'Failed to read the file' in /usr/share/openmediavault/engined/rpc/docker.inc:1504
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/docker.inc(0): Imagick->__construct()
#1 [internal function]: OMVRpcServiceDocker->syncDockerLogos(NULL, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('syncDockerLogos', NULL, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'syncDockerLogos', NULL, Array, 1)
#5 {main}
Alles anzeigen
Here is the snip from the "update management history log":
Start-Date: 2017-12-30 16:47:10
Commandline: apt-get --yes --force-yes --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::=--force-confold install docker-ce
Upgrade: docker-ce:amd64 (17.09.1~ce-0~debian, 17.12.0~ce-0~debian)
End-Date: 2017-12-30 16:47:18
I restarted the docker service, but the message is still there. Seemingly everything works as expected.
Do you need any other informations to repair this?
Greetings Hoppel
It looks like it fails to download a picture from github (thumbnail used in the repo tab). It should not affect the functionality of the plug-in though.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!