Failed Docker installation on a fresh OMV 4

  • Hey Gang,


    Just got HC2 this week and been playing with it. Today it felt like I broke it and decided to re-flash the microSD card with a fresh image of OMV4.


    Been setting up everything according to Techno Dad's videos. Today after enabling Docker-se in the OMV Extras and trying to install the Docker plugin I'm getting nowhere for some reason. Below is an error log, hopefully someone can recommend a solution.


    • Official Post

    The update installed fine on my test VM. I will have to try it on a fresh install but I don't think the update is the problem.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    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!

  • I'm having the same problem (On a Odroid XU4), fresh image (and after installing all OS updates), updated extras, instaled plugin and get this:


    ...
    Fetched 32.6 MB in 21s (1554 kB/s)
    Selecting previously unselected package liblqr-1-0:armhf.
    (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 48578 files and directories currently installed.)
    Preparing to unpack .../00-liblqr-1-0_0.4.2-2+b2_armhf.deb ...
    Unpacking liblqr-1-0:armhf (0.4.2-2+b2) ...
    Selecting previously unselected package libfftw3-double3:armhf.
    Preparing to unpack .../01-libfftw3-double3_3.3.5-3_armhf.deb ...
    Unpacking libfftw3-double3:armhf (3.3.5-3) ...
    Selecting previously unselected package liblcms2-2:armhf.
    Preparing to unpack .../02-liblcms2-2_2.8-4+deb9u1_armhf.deb ...
    Unpacking liblcms2-2:armhf (2.8-4+deb9u1) ...
    Selecting previously unselected package libopenjp2-7:armhf.
    Preparing to unpack .../03-libopenjp2-7_2.1.2-1.1+deb9u2_armhf.deb ...
    Unpacking libopenjp2-7:armhf (2.1.2-1.1+deb9u2) ...
    Selecting previously unselected package imagemagick-6-common.
    Preparing to unpack .../04-imagemagick-6-common_8%3a6.9.7.4+dfsg-11+deb9u6_all.deb ...
    Unpacking imagemagick-6-common (8:6.9.7.4+dfsg-11+deb9u6) ...
    Selecting previously unselected package libmagickcore-6.q16-3:armhf.
    Preparing to unpack .../05-libmagickcore-6.q16-3_8%3a6.9.7.4+dfsg-11+deb9u6_armhf.deb ...
    Unpacking libmagickcore-6.q16-3:armhf (8:6.9.7.4+dfsg-11+deb9u6) ...
    Selecting previously unselected package libmagickwand-6.q16-3:armhf.
    Preparing to unpack .../06-libmagickwand-6.q16-3_8%3a6.9.7.4+dfsg-11+deb9u6_armhf.deb ...
    Unpacking libmagickwand-6.q16-3:armhf (8:6.9.7.4+dfsg-11+deb9u6) ...
    Selecting previously unselected package containerd.io.
    Preparing to unpack .../07-containerd.io_1.2.2-1_armhf.deb ...
    Unpacking containerd.io (1.2.2-1) ...
    Selecting previously unselected package docker-ce-cli.
    Preparing to unpack .../08-docker-ce-cli_5%3a18.09.1~3-0~debian-stretch_armhf.deb ...
    Unpacking docker-ce-cli (5:18.09.1~3-0~debian-stretch) ...
    Selecting previously unselected package docker-ce.
    Preparing to unpack .../09-docker-ce_5%3a18.09.1~3-0~debian-stretch_armhf.deb ...
    Unpacking docker-ce (5:18.09.1~3-0~debian-stretch) ...
    Selecting previously unselected package php-symfony-polyfill-apcu.
    Preparing to unpack .../10-php-symfony-polyfill-apcu_1.2.0-1_all.deb ...
    Unpacking php-symfony-polyfill-apcu (1.2.0-1) ...
    Selecting previously unselected package php-symfony-class-loader.
    Preparing to unpack .../11-php-symfony-class-loader_2.8.7+dfsg-1.3+deb9u1_all.deb ...
    Unpacking php-symfony-class-loader (2.8.7+dfsg-1.3+deb9u1) ...
    Selecting previously unselected package omvextras-common.
    Preparing to unpack .../12-omvextras-common_4.0.1_all.deb ...
    Unpacking omvextras-common (4.0.1) ...
    Selecting previously unselected package php7.0-curl.
    Preparing to unpack .../13-php7.0-curl_7.0.33-0+deb9u1_armhf.deb ...
    Unpacking php7.0-curl (7.0.33-0+deb9u1) ...
    Selecting previously unselected package php-curl.
    Preparing to unpack .../14-php-curl_1%3a7.0+49_all.deb ...
    Unpacking php-curl (1:7.0+49) ...
    Selecting previously unselected package php-imagick.
    Preparing to unpack .../15-php-imagick_3.4.3~rc2-2_armhf.deb ...
    Unpacking php-imagick (3.4.3~rc2-2) ...
    Selecting previously unselected package openmediavault-docker-gui.
    Preparing to unpack .../16-openmediavault-docker-gui_4.1.1_all.deb ...
    Unpacking openmediavault-docker-gui (4.1.1) ...
    Setting up imagemagick-6-common (8:6.9.7.4+dfsg-11+deb9u6) ...
    Setting up libopenjp2-7:armhf (2.1.2-1.1+deb9u2) ...
    Setting up containerd.io (1.2.2-1) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
    Setting up liblcms2-2:armhf (2.8-4+deb9u1) ...
    Setting up php7.0-curl (7.0.33-0+deb9u1) ...


    Creating config file /etc/php/7.0/mods-available/curl.ini with new version
    Setting up libfftw3-double3:armhf (3.3.5-3) ...
    Processing triggers for php7.0-fpm (7.0.33-0+deb9u1) ...


    >>> *************** Error ***************
    Bad Gateway
    <<< *************************************
    Setting up liblqr-1-0:armhf (0.4.2-2+b2) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Setting up php-symfony-polyfill-apcu (1.2.0-1) ...
    Processing triggers for systemd (232-25+deb9u6) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    Processing triggers for openmediavault (4.1.17-1) ...
    Restarting engine daemon ...
    Setting up docker-ce-cli (5:18.09.1~3-0~debian-stretch) ...
    Setting up docker-ce (5:18.09.1~3-0~debian-stretch) ...


    Configuration file '/etc/default/docker'
    ==> File on system created by you or by a script.
    ==> File also in package provided by package maintainer.
    What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
    D : show the differences between the versions
    Z : start a shell to examine the situation
    The default action is to keep your current version.
    *** docker (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package docker-ce (--configure):
    end of file on stdin at conffile prompt
    dpkg: dependency problems prevent configuration of openmediavault-docker-gui:
    openmediavault-docker-gui depends on docker-ce (>= 5:18.09); however:
    Package docker-ce is not configured yet.
    openmediavault-docker-gui depends on docker-ce (<< 5:18.10); however:
    Package docker-ce is not configured yet.


    dpkg: error processing package openmediavault-docker-gui (--configure):
    dependency problems - leaving unconfigured
    Setting up libmagickcore-6.q16-3:armhf (8:6.9.7.4+dfsg-11+deb9u6) ...
    Setting up php-curl (1:7.0+49) ...
    Setting up php-symfony-class-loader (2.8.7+dfsg-1.3+deb9u1) ...
    Setting up libmagickwand-6.q16-3:armhf (8:6.9.7.4+dfsg-11+deb9u6) ...
    Setting up omvextras-common (4.0.1) ...
    Setting up php-imagick (3.4.3~rc2-2) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for openmediavault (4.1.17-1) ...
    Updating file permissions ...
    Purging internal cache ...
    Restarting engine daemon ...
    Errors were encountered while processing:
    docker-ce
    openmediavault-docker-gui

  • Hey guys,


    I get a similar problem on my sytem. I use a Debian 4.9 (because there is no UEFI bootable version of OMV yet) and installed a OMV 4.1.15-1 (Arrakis) on top of it.
    I tried installing docker-gui via the webinterface. My Log is missing "Bad Gateway" and the first error seems to be in a different position. After unsuccesfull installation the webinterface info box with installer information is spamming:
    >>> *************** Error ***************
    <<< *************************************


    Logfile:

    • Official Post

    As someone who has installed this more than once I see the same error in all the above;


    Errors were encountered while processing:
    docker-ce
    openmediavault-docker-gui


    This would suggest that the Docker-ce and the docker plugin were being installed at the same time!


    The process should be OMV-Extras -> Docker-ce -> Edit -> Enable -> Save this will bring up a progress box indicating that Docker-ce is being installed, when completed the progress box closes indicating the installation is complete.
    Then and only then install the Docker plugin.


    Remove/uninstall the plugin, then apt clean from OMV-Extras, disable Docker-ce, save, apt clean from OMV-Extras, then try again. Whilst this should work seamlessly I have seen users have problems installing Docker on a Pi but they have been able to install on a VM running OMV on another machine.

  • Ok i got it working, i followed this instructions:


    External Content gist.github.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    Specifically this commands in ssh:


    wget -O- http://neuro.debian.net/lists/wheezy.us-ca.libre | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list
    sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80 0xA5D32F012649A5A9


    sudo apt-get update


    sudo apt-get install init-system-helpers


    sudo apt-get install virtualbox


    wget -qO- https://get.docker.com/ | sh


    COMPOSE_VERSION=`git ls-remote https://github.com/docker/compose | grep refs/tags | grep -oP "[0-9]+\.[0-9][0-9]+\.[0-9]+$" | tail -n 1`
    sudo sh -c "curl -L https://github.com/docker/compose/releases/download/${COMPOSE_VERSION}/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose"
    sudo chmod +x /usr/local/bin/docker-compose
    sudo sh -c "curl -L https://raw.githubusercontent.com/docker/compose/${COMPOSE_VERSION}/contrib/completion/bash/docker-compose > /etc/bash_completion.d/docker-compose"


    dpkg --remove --force-remove-reinstreq pacote



    ----------------------------------------------------------------------------------------------------------------------------------


    Then i downloaded the .deb for 4.x version from "http://omv-extras.org/joomla/index.php/guides" and in web interface did this:


    uploaded .deb to plugins (again, because i've already done this several times)


    enabled docker omv extras (again)


    enabled plugin (again)


    and worked!

  • Remove/uninstall the plugin, then apt clean from OMV-Extras, disable Docker-ce, save, apt clean from OMV-Extras, then try again. Whilst this should work seamlessly I have seen users have problems installing Docker on a Pi but they have been able to install on a VM running OMV on another machine.

    Hi geaves,


    I did this. Afterwards I followed your instruction:


    The process should be OMV-Extras -> Docker-ce -> Edit -> Enable -> Save this will bring up a progress box indicating that Docker-ce is being installed, when completed the progress box closes indicating the installation is complete.
    Then and only then install the Docker plugin.

    After Enabling docker-ce and saving nothing happens (despite the green indicator for the active module being set). No progress bar or info box appears. What am I doing wrong?
    I even hit update after enabling and saving docker-ce. Ocassionally this fails with

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update ': Reading package lists...

    But refreshing the webinterface fixes this. No idea why this is happening though...


    FYI: I did this the same way the first time trying to install it (1. activate docker-ce in OMV extras, 2. Install docker-gui from extensions)


    cheers
    maverick757

    • Official Post

    After Enabling docker-ce and saving nothing happens

    When you select Docker-CE and click edit to enable it you will see Repo #1 and Repo #2 these are the repositories where Docker is being downloaded from, if nothing happens then it's simply not downloading.


    The error might be dns related, if you go into network -> interfaces select yours and click edit scroll down dns servers, normally there is nothing in there if using dhcp.....now from memory when I first did my install it used dhcp but I added a public dns server anyway. You could also try clearing your browser cache that seems to cure a lot of errors.


    With that spamming error I've experienced the same, doing an apt clean, then an omv-update, then another apt clean from OMV-Extras seems to clear it.

  • sudo apt-get install virtualbox

    Hello, why did you install Virtualbox?



    Quote

    wget -O- neuro.debian.net/lists/wheezy.us-ca.libre | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list

    This is not a goog idee, to use external sources.


    Use a terminal to install docker, if you install the Docker container "portainer", you have a nice docker-gui.


    "docker omv extras" makes many problems, Cups, Docker doesn't work by me.


    om

    • Official Post

    On a fresh installation, installing the plugin from the web interface does fail although it is easily fixed by apt-get -f install and answer yes to the replace /etc/default/docker question. Installing docker-ce first is a bad idea because you might install a version of docker too new for the plugin and a downgrade might go badly.



    So, I think the plugin either needs to stop editing /etc/default/docker on install.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    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!

  • I got the same issue and solved it by installing docker-ce via terminal (apt-get install docker-ce) and after that installing the plugin.

    Thanks, that did it for me. Enable docker-ce repo in omv-extras and then run 'apt-get install docker-ce' from terminal. Then docker-gui plugin installs without a problem.

    • Official Post

    run 'apt-get install docker-ce' from terminal. Then docker-gui plugin installs without a problem.

    That works until a newer version than 18.09 is released and that will happen soon. I'm looking at a fix for the plugin. Until then, I recommend using my method above.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    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!

  • That works until a newer version than 18.09 is released and that will happen soon. I'm looking at a fix for the plugin. Until then, I recommend using my method above.

    Ooh. Maybe thats what im experiencing right now. I'm trying to run mariadb docker, but keep getting 'exit code 2'

  • On a fresh installation, installing the plugin from the web interface does fail although it is easily fixed by apt-get -f install and answer yes to the replace /etc/default/docker question. Installing docker-ce first is a bad idea because you might install a version of docker too new for the plugin and a downgrade might go badly.

    Cheers! That worked like a charm :)

  • On a fresh installation, installing the plugin from the web interface does fail although it is easily fixed by apt-get -f install and answer yes to the replace /etc/default/docker question. Installing docker-ce first is a bad idea because you might install a version of docker too new for the plugin and a downgrade might go badly.

    Can you help me out? I'm trying installing Docker again after removing it.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!