Docker on rPi3B+ not working

    Hi All


    OMV4 on rPi 3B+
    Static IP 192.168.1.135


    Completely new user. Excited to get my NAS running and connecting from my win PC, etc.


    I am having a problem to get Docker running, which, from what I understand, is the 'platform' that many other apps run on as 'containers' ( hope I got that right )


    did installation for the OMV4 version as instructed here :
    http://omv-extras.org/joomla/index.php/guides


    It failed with this info :

    Code
    >>> *************** 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 --allow-downgrades --allow-change-held-packages --fix-missing --allow-unauthenticated --reinstall install openmediavault-docker-gui 2>&1' with exit code '100': E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
<<< *************************************


    used Putty to login as root and ran :
    dpkg --configure -a


    did not get any odd feedback from that.


    then web interface > plugins > docker > install


    this appeared to install and is listed in 'Services', but see below for the info screen displayed ( something odd at the end - full log in the attached filedocker install info.txt )


    after that :
    added a container for Cloud Commander and followed the video instructions to set up.


    In my browser, I can't connect to :
    http://192.168.1.135:8000/


    in the CloudCommander container log :
    standard_init_linux.go:207: exec user process caused "exec format error"


    I did also try adding FileZilla to Docker and that also would not run.


    Please can a guru tell me where I have gone wrong, and how to correct this so that Docker runs correctly ?


    Quote from DaveOB

    did installation for the OMV4 version as instructed here :
    omv-extras.org/joomla/index.php/guides

    There's no need to install OMV-Extras if you use the 'official' RPi image: https://sourceforge.net/projec…/Raspberry%20Pi%20images/


    Quote from DaveOB

    exec user process caused "exec format error"

    You're trying to run an x86 container on ARM. You need an armhf variant instead. And the 'weakref.py' warning is harmless. You can fix it though in a SSH session as root doing this:

    Code
    wget -O /usr/lib/python3.5/weakref.py https://raw.githubusercontent.com/python/cpython/9cd7e17640a49635d1c1f8c2989578a8fc2c1de6/Lib/weakref.py

    Thanks tkaiser. Really appreciate the reply and insight


    I did use the RPi image you mentioned, but the first time I tried with Etcher, it brick'd my SD card.
    Had to buy a new card, so extracted the image and burned it using Rufus


    Ran the weakref fix you supplied and don't see any obvious errors :

    Code
    root@OMVpi1:~# wget -O /usr/lib/python3.5/weakref.py https://raw.githubusercontent.com/python/cpython/9cd7e17640a49635d1c1f8c2989578a8fc2c1de6/Li
b/weakref.py                                                                                                                                     
--2019-06-04 12:16:56--  https://raw.githubusercontent.com/python/cpython/9cd7e17640a49635d1c1f8c2989578a8fc2c1de6/Lib/weakref.py                
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.172.133                                                               
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.172.133|:443... connected.                                           
HTTP request sent, awaiting response... 200 OK                                                                                                   
Length: 20466 (20K) [text/plain]                                                                                                                 
Saving to: ‘/usr/lib/python3.5/weakref.py’                                                                                                       
/usr/lib/python3.5/weakref.py        100%[===================================================================>]  19.99K  --.-KB/s    in 0.05s    
2019-06-04 12:16:57 (441 KB/s) - ‘/usr/lib/python3.5/weakref.py’ saved [20466/20466]


    <quote>
    You're trying to run an x86 container on ARM. You need an armhf variant instead.
    <end quote>


    Are you talking about the containers like filezilla and Cloud Commander ?
    If so, where would I search for a armhf variant for these ( most interesed in Cloud Commander to be able to move files on the PI USB HDD between folders without having to route thru the PC )

    Quote from DaveOB

    I did use the RPi image you mentioned, but the first time I tried with Etcher, it brick'd my SD card

    Etcher doesn't brick SD cards, it only reports failing SD cards (or other flash media). That's the benefits of Etcher verifying what should've been written to the card. Other tools that skip verify happily write garbage.


    As for the Container questions I've no idea but the forum search in the upper right should be sufficient since what you experienced ('exec format error') is quite common with Docker + RPi.

    Thanks again.


    I think the problem with Etcher was that I bumped and dislodged the SD card adaptor on my PC during the verify process. After that the SD card was dead. So I wasn't wanting to risk destroying another SD card.


    For the 'exec format' problem, do I understand correctly that it isn't a problem related to the Docker platform itself, but actually a problem with the apps being loading in to the containers being for x86 instead of ARM ?


    Thank you again for your guidance

    Quote from DaveOB

    For the 'exec format' problem, do I understand correctly that it isn't a problem related to the Docker platform itself, but actually a problem with the apps being loading in to the containers being for x86 instead of ARM ?

    Yes, since you're running on an armhf platform only stuff also made for this platform can run inside containers (since otherwise a CPU emulation would be required for which the RPi is way too slow).


    BTW: Etcher isn't destroying SD cards. Most probably a simple coincidence and your SD card died for the usual reasons (e.g. old or counterfeit card)

    <quote>
    BTW: Etcher isn't destroying SD cards. Most probably a simple coincidence and your SD card died for the usual reasons (e.g. old or counterfeit card)
    <end quote>


    Yes, it was a reasonably aged card and had been used etensively in a 3D printer for around 3 years.


    My apologies to Etcher for implying it was at fault. The cause was most certainly either 'Murphy's Law' or a User "ID 10 T" error.


    Thanks for clearing up the confusion about the different platforms

Participate now!

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

Register Yourself Login