Can't get any Docker containers to run on Nano Pi Neo2 (Arm64v8) on Armbian Buster

  • Hi All,
    I've got Arbian Buster running on a Nano Pi Neo2 in a NEO Station NS-120B (their 1 drive micro NAS). I was able to get Docker and Portainer working on it, but every image I've tried so far crashes even before it has a chance to log anything (or at least I'm not getting any logs in Portainer. I tried an Alpine Arm64v8 docker image just now and that does the same thing.


    Any suggestions appeciated. I'm a noob to Docker.


    Thanks
    JD

  • Do you have any container logs you can look at? Portainer will show them to you. Look in the container list under quick actions. Click on first icon on the left.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Also, since Portainer is deployed as a docker, and it is working, So check the build info in the image details and post them.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • OK.. so I just did a docker run haugene/transmission-openvpn:latest-armhf and got the following in the syslog:


    Dec 16 11:45:37 nanopineo2 systemd[8156]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099\x2dinit-merged.mount: Succeeded.
    Dec 16 11:45:37 nanopineo2 systemd[1]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099\x2dinit-merged.mount: Succeeded.
    Dec 16 11:45:37 nanopineo2 systemd[8156]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099-merged.mount: Succeeded.
    Dec 16 11:45:37 nanopineo2 systemd[1]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099-merged.mount: Succeeded.
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9579]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9579]: Using default interface naming scheme 'v240'.
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9579]: Could not generate persistent MAC address for veth9f7abce: No such file or directory
    Dec 16 11:45:37 nanopineo2 kernel: [11868.605230] docker0: port 2(veth55b8d68) entered blocking state
    Dec 16 11:45:37 nanopineo2 kernel: [11868.605242] docker0: port 2(veth55b8d68) entered disabled state
    Dec 16 11:45:37 nanopineo2 kernel: [11868.605735] device veth55b8d68 entered promiscuous mode
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9581]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9581]: Using default interface naming scheme 'v240'.
    Dec 16 11:45:37 nanopineo2 systemd-udevd[9581]: Could not generate persistent MAC address for veth55b8d68: No such file or directory
    Dec 16 11:45:37 nanopineo2 networkd-dispatcher[1465]: WARNING:Unknown index 12 seen, reloading interface list
    Dec 16 11:45:38 nanopineo2 containerd[1495]: time="2019-12-16T11:45:38.231623693-05:00" level=info msg="shim containerd-shim started" address="/containerd-shim/moby/83cb4317a979cbe1a83fb267d4ac446a8a2497f0a1b2b175e4fd46080d725180/shim.sock" debug=false pid=9594
    Dec 16 11:45:39 nanopineo2 kernel: [11869.808821] eth0: renamed from veth9f7abce
    Dec 16 11:45:39 nanopineo2 kernel: [11869.832148] docker0: port 2(veth55b8d68) entered blocking state
    Dec 16 11:45:39 nanopineo2 kernel: [11869.832178] docker0: port 2(veth55b8d68) entered forwarding state
    Dec 16 11:45:39 nanopineo2 systemd-networkd[543]: veth55b8d68: Gained carrier
    Dec 16 11:45:39 nanopineo2 containerd[1495]: time="2019-12-16T11:45:39.897786077-05:00" level=info msg="shim reaped" id=83cb4317a979cbe1a83fb267d4ac446a8a2497f0a1b2b175e4fd46080d725180
    Dec 16 11:45:39 nanopineo2 dockerd[1496]: time="2019-12-16T11:45:39.907113803-05:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
    Dec 16 11:45:39 nanopineo2 systemd-networkd[543]: veth55b8d68: Lost carrier
    Dec 16 11:45:39 nanopineo2 kernel: [11870.756698] docker0: port 2(veth55b8d68) entered disabled state
    Dec 16 11:45:39 nanopineo2 kernel: [11870.756997] veth9f7abce: renamed from eth0
    Dec 16 11:45:40 nanopineo2 systemd-udevd[9579]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    Dec 16 11:45:40 nanopineo2 networkd-dispatcher[1465]: WARNING:Unknown index 11 seen, reloading interface list
    Dec 16 11:45:40 nanopineo2 kernel: [11870.890174] docker0: port 2(veth55b8d68) entered disabled state
    Dec 16 11:45:40 nanopineo2 kernel: [11870.893106] device veth55b8d68 left promiscuous mode
    Dec 16 11:45:40 nanopineo2 kernel: [11870.893137] docker0: port 2(veth55b8d68) entered disabled state
    Dec 16 11:45:40 nanopineo2 networkd-dispatcher[1465]: Failed to request link: No such device
    Dec 16 11:45:40 nanopineo2 networkd-dispatcher[1465]: ERROR:Failed to get interface "veth55b8d68" status: Command '['/bin/networkctl', 'status', '--no-pager', '--no-legend', '--', 'veth55b8d68']' returned non-zero exit status 1.
    Dec 16 11:45:40 nanopineo2 systemd[8156]: run-docker-netns-814d329ed0c3.mount: Succeeded.
    Dec 16 11:45:40 nanopineo2 systemd[1]: run-docker-netns-814d329ed0c3.mount: Succeeded.
    Dec 16 11:45:40 nanopineo2 dockerd[1496]: time="2019-12-16T11:45:40.246569974-05:00" level=warning msg="83cb4317a979cbe1a83fb267d4ac446a8a2497f0a1b2b175e4fd46080d725180 cleanup: failed to unmount IPC: umount /data/Docker/containers/83cb4317a979cbe1a83fb267d4ac446a8a2497f0a1b2b175e4fd46080d725180/mounts/shm, flags: 0x2: no such file or directory"
    Dec 16 11:45:40 nanopineo2 systemd[8156]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099-merged.mount: Succeeded.
    Dec 16 11:45:40 nanopineo2 systemd[1]: data-Docker-overlay2-6aa6171e5e0628938f5839b7169c678603534ad0c73ab5a0746c946d039e5099-merged.mount: Succeeded.


    this looks to be similar to what I got when I tried running arm64v8/alpine:latest as well.


    As for build info for the image would that be this?


    1104.4 MB
    ADD file:00c70d8bc8c53546354020041a81f03afd632bf75797b23ee4988fbfe77bd507 in /
    2350 B
    COPY file:7e96bef641cb464ab5ecebb3e587e9602e44343ea6ef5053120a1bc89b195904 in /etc/dpkg/dpkg.cfg.d/
    399 B
    COPY file:fee64614e449c34ea8ea69a2f3263d8c44f49bd0bee3761919ca8e29080c755c in /etc/apt/apt.conf.d/
    41.6 kB
    COPY file:b81b206f367577d07897d50c931155c1401be3d76df33fa9321914bb3ce5bc5c in /usr/bin/entry.sh
    50 B
    RUN mkdir -p /usr/share/man/man1
    60 B
    ENV LC_ALL=C.UTF-8
    70 B
    ENV PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    80 B
    ENV DEBIAN_FRONTEND=noninteractive
    90 B
    ENV UDEV=off
    100 B
    LABEL io.balena.architecture=rpi io.balena.qemu.version= io.balena.device-type=raspberrypi
    110 B
    ENV QEMU_CPU=arm1176
    12379 B
    RUN echo '#!/bin/sh\nset -e\nset -u\nexport DEBIAN_FRONTEND=noninteractive\nn=0\nmax=2\nuntil [ $n -gt $max ]; do\n set +e\n ...
    1318.2 MB
    RUN install_packages libraspberrypi-bin
    140 B
    ENTRYPOINT ["/usr/bin/entry.sh"]
    150 B
    CMD ["/bin/bash"]
    160 B
    LABEL io.balena.architecture=rpi
    170 B
    LABEL io.balena.qemu.version=4.0.0+balena-arm
    185.6 MB
    COPY file:2c501ba7ec1ca6440a43b3582ec43336e488756d8def550195796d0b6794bea4 in /usr/bin
    193.1 MB
    RUN apt-get update && apt-get install -y --no-install-recommends sudo ca-certificates findutils gnupg dirmngr inetu...
    201.6 MB
    RUN curl -SLO "http://resin-packages.s3.amazonaws.com/resin-xbuild/v1.0.0/resin-xbuild1.0.0.tar.gz" && echo "1eb099bc3176ed07...
    210 B
    ENV LC_ALL=C.UTF-8
    220 B
    ENV DEBIAN_FRONTEND=noninteractive
    230 B
    ENV UDEV=off
    24297 B
    RUN echo 'path-exclude /usr/share/doc/*\npath-include /usr/share/doc/*/copyright\npath-exclude /usr/share/man/*\npath-exclude /...
    2599 B
    RUN echo 'APT::Get::Assume-Yes "true";\nAPT::Install-Recommends "0";\nAPT::Install-Suggests "0";\nquiet "true";' > /etc/apt/apt...
    260 B
    RUN mkdir -p /usr/share/man/man1
    271.6 kB
    COPY file:288db2746ee38250e86eeca89bea8ee45bebb7874bcdce941c41babba1764fc6 in /usr/bin/entry.sh
    280 B
    ENTRYPOINT ["/usr/bin/entry.sh"]
    290 B
    LABEL io.balena.device-type=raspberry-pi
    3035.5 MB
    RUN apt-get update && apt-get install -y --no-install-recommends less kmod nano net-tools ifupdown iputils-ping i...
    311.6 MB
    cross-build-start
    320 B
    VOLUME [/data]
    330 B
    VOLUME [/config]
    3456.6 MB
    RUN apt-get update && apt-get -y install apt-utils && apt-get -y install transmission-cli transmission-common transmiss...
    3517.8 MB
    ADD dir:1ad1fe26a95c22c386eb0da8ff3b11a3e42d517ce3e24e47da49bdada287b405 in /etc/openvpn/
    3622.2 kB
    ADD dir:3760cda9b21d647b2f1d671f5e0062578484fa440fb1d454a73603f6608bb834 in /etc/transmission/
    371.7 kB
    ADD dir:a171ce93e6c864c044b266b1b3c42ef04618bce4d152be26b1e3feeb34de2869 in /opt/tinyproxy/
    38446 B
    ADD dir:2a5ace1ebb4d5c2860cf90ea210aa78777faa8625332b3ff096755aacc64d238 in /etc/scripts/
    390 B
    ENV OPENVPN_USERNAME=**None** OPENVPN_PASSWORD=**None** OPENVPN_PROVIDER=**None** GLOBAL_APPLY_PERMISSIONS=true TRANSMISSION_A...
    400 B
    EXPOSE 9091/tcp
    410 B
    CMD ["dumb-init" "/etc/openvpn/start.sh"]
    424 B
    cross-build-end

  • That syslog doesn't mean anything to me, sorry.


    You might try removing Portainer and installing it again.


    Also, if you are going to test with images don't try highly complex ones like haugene/transmission-openvpn.


    Try something simple. Run this command in the shell and see what happens:


    docker run hello-world

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • OK.. that appears to work:


    from the log:


    Hello from Docker!
    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.
    (arm64v8)
    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.


    To try something more ambitious, you can run an Ubuntu container with:
    $ docker run -it ubuntu bash


    Share images, automate workflows, and more with a free Docker ID:
    https://hub.docker.com/


    For more examples and ideas, visit:
    https://docs.docker.com/get-started/




    running the Ubuntu container seems to work also:


    root@nanopineo2:~# docker run -it ubuntu bash
    Unable to find image 'ubuntu:latest' locally
    latest: Pulling from library/ubuntu
    6531af355894: Pull complete
    82f7942d2fb7: Pull complete
    fdce94e690d5: Pull complete
    a96a89ada1c3: Pull complete
    Digest: sha256:6e9f67fa63b0323e9a1e587fd71c561ba48a034504fb804fd26fd8800039835d
    Status: Downloaded newer image for ubuntu:latest
    root@0833fe7e9fa7:/# pwd
    /
    root@0833fe7e9fa7:/# hostname
    0833fe7e9fa7
    root@0833fe7e9fa7:/# ls
    bin boot dev etc home lib media mnt opt proc root run sbin srv sys tmp usr var
    root@0833fe7e9fa7:/# df -h
    Filesystem Size Used Avail Use% Mounted on
    overlay 1.9T 2.4G 1.9T 1% /
    tmpfs 64M 0 64M 0% /dev
    tmpfs 495M 0 495M 0% /sys/fs/cgroup
    shm 64M 0 64M 0% /dev/shm
    /dev/sda1 1.9T 2.4G 1.9T 1% /etc/hosts
    tmpfs 495M 0 495M 0% /proc/asound
    tmpfs 495M 0 495M 0% /sys/firmware
    root@0833fe7e9fa7:/#

  • Since you have successfully run some docker and successful added some to Portainer, about the only thing left I can think of is that perhaps for the images that fail you are not pulling for the correct architecture that matches your hardware.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Yeah, that's what I'm thinking.. I found another Transmission image (linuxserver/transmission) that has an Arm64 version and uses the Docker manifest to select the appropriate version. They also have a script to add openvpn to it, so hopefully it will do the job.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!