Docker install on ARM6 (Raspberry PI 1 and Old Pi W) fails

[nicholasrobertm]

Appreciate any help with this, I've left as much detail below as I can, but if there is something needed I've missed please let me know!

• This is a bug report
• This is a feature request
• I searched existing issues before opening this one

Expected behavior

Docker/dockerd is able to run after install

Actual behavior

Install completes but docker fails to start

Steps to reproduce the behavior

Install latest raspbian lite image on either:
Raspberry pi zero w v1.1
Raspberry pi 1 2011.12

Do sudo apt-get update on either
Do sudo apt-get upgrade
Use curl and execute docker install script via:
curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh
Give pi user docker group access
sudo usermod -aG docker pi
Run hello-world docker container via:
docker run hello-world

Output of docker version:

pi@pi4:~ $ docker version
Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:57:21 2018
 OS/Arch:           linux/arm
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Output of docker info:

pi@pi4:~ $ docker info
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Output of systemctl start docker:

Job for docker.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status docker.service" and "journalctl -xe" for details.```

**Output of `systemctl status docker.service`:**
```pi@pi4:~ $ systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: core-dump) since Fri 2018-11-16 02:14:44 UTC; 1min 5s ago
     Docs: https://docs.docker.com
  Process: 4013 ExecStart=/usr/bin/dockerd -H unix:// (code=dumped, signal=SEGV)
 Main PID: 4013 (code=dumped, signal=SEGV)
      CPU: 422ms

Nov 16 02:14:44 pi4 systemd[1]: docker.service: Unit entered failed state.
Nov 16 02:14:44 pi4 systemd[1]: docker.service: Failed with result 'core-dump'.
Nov 16 02:14:44 pi4 systemd[1]: Stopped Docker Application Container Engine.```

**Output of `journalctl -xe`:**

```pi@pi4:~ $ journalctl -xe
-- Support: https://www.debian.org/support
-- 
-- Unit polkit.service has begun starting up.
Nov 16 02:14:38 pi4 polkitd[4001]: started daemon version 0.105 using authority implementation `local' ve
Nov 16 02:14:38 pi4 dbus[204]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Nov 16 02:14:38 pi4 systemd[1]: Started Authorization Manager.
-- Subject: Unit polkit.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit polkit.service has finished starting up.
-- 
-- The start-up result is done.
Nov 16 02:14:38 pi4 polkitd(authority=local)[4001]: Registered Authentication Agent for unix-process:3996
Nov 16 02:14:40 pi4 polkitd(authority=local)[4001]: Unregistered Authentication Agent for unix-process:39
Nov 16 02:14:40 pi4 polkitd(authority=local)[4001]: Operator of unix-process:3996:145604 FAILED to authen
Nov 16 02:14:43 pi4 sudo[4007]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl 
Nov 16 02:14:43 pi4 sudo[4007]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Nov 16 02:14:43 pi4 systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has begun starting up.
Nov 16 02:14:43 pi4 systemd[1]: Starting containerd container runtime...
-- Subject: Unit containerd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit containerd.service has begun starting up.
Nov 16 02:14:43 pi4 systemd[1]: Started containerd container runtime.
-- Subject: Unit containerd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit containerd.service has finished starting up.
-- 
-- The start-up result is done.
Nov 16 02:14:44 pi4 systemd[1]: docker.service: Main process exited, code=dumped, status=11/SEGV
Nov 16 02:14:44 pi4 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
Nov 16 02:14:44 pi4 systemd[1]: docker.service: Unit entered failed state.
Nov 16 02:14:44 pi4 sudo[4007]: pam_unix(sudo:session): session closed for user root
Nov 16 02:14:44 pi4 systemd[1]: docker.service: Failed with result 'core-dump'.
Nov 16 02:14:44 pi4 systemd[1]: containerd.service: Main process exited, code=dumped, status=4/ILL
Nov 16 02:14:44 pi4 systemd[1]: containerd.service: Unit entered failed state.
Nov 16 02:14:44 pi4 systemd[1]: containerd.service: Failed with result 'core-dump'.
Nov 16 02:14:44 pi4 systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has finished shutting down.```

**Additional environment details (AWS, VirtualBox, physical, etc.)**
Physical, Tried both on a raspberry pi 1 2011.12 and a pi zero w v1.1

[shuchow]

I'm having the exact same issue with the same log outputs. I'm running a Raspberry Pi 3 with four Raspberry Pi Zeros via a Clusterhat.

Docker installed and runs on the Pi 3 just fine. The Pi Zeros (v. 1.2) core dumps when docker attempts to start.

[thaJeztah]

Thanks for reporting! This looks to be a duplicate of moby/moby#38175, which has some more information. It appears to be that there's a packaging issue in the builds for the 18.09 release. The packaging team is looking at getting that fixed for a 18.09.1 patch release, but in the meantime, you can install the previous (18.06.1) version of docker, which should work (see moby/moby#38175 (comment)).

Please subscribe to moby/moby#38175 I'm locking the conversation on this ticket so that the discussion doesn't diverge, but feel free to participate in the issue I linked to.

(I'll keep this issue opened, because it's not resolved yet, and so that it's easier to find for people)

[thaJeztah]

This should be resolved now with the container.io_1.2.10-2 package; moby/moby#38175 (comment)

Hey guys!

Just released new containerd.io package version 1.2.10-2 to the https://download.docker.com repositories, please let me know if that resolves all issues related to this segmentation fault, I do not currently have a armv6 machine to test on.

Sorry for the late update on this, hopefully this issue is now resolved