I'm using a Raspberry Pi 1 Model B.
I've just installed using the easy script:
curl -sSL https://get.docker.com | sh
install results:
# Executing docker install script, commit: 4957679
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] https://download.docker.com/linux/raspbian stretch edge" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:
sudo usermod -aG docker jimjamz
Remember that you will have to log out and back in for this to take effect!
WARNING: Adding a user to the "docker" group will grant the ability to run
containers which can be used to obtain root privileges on the
docker host.
Refer to https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
for more information.
added my user to the docker group:
sudo usermod -aG docker jimjamz
logged out, logged back in and I wanted to confidence check docker:
docker -v
result:
Docker version 18.09.0, build 4d60db4
but when I want to use any other docker command:
docker ps -a
result:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
checking the status of the 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 Sat 2019-01-26 14:45:07 UTC; 14min ago
Docs: https://docs.docker.com
Process: 4314 ExecStart=/usr/bin/dockerd -H unix:// (code=dumped, signal=SEGV)
Main PID: 4314 (code=dumped, signal=SEGV)
CPU: 668ms
checking the journal for further info:
sudo journalctl -qxe | grep docker
result:
Jan 26 14:44:33 JIMJAMZ-PI sudo[4215]: jimjamz : TTY=pts/0 ; PWD=/home/jimjamz ; USER=root ; COMMAND=/usr/bin/docker ps -a
Jan 26 14:44:49 JIMJAMZ-PI sudo[4248]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service docker restart
-- Subject: Unit docker.service has begun start-up
-- Unit docker.service has begun starting up.
Jan 26 14:44:53 JIMJAMZ-PI systemd[1]: docker.service: Main process exited, code=dumped, status=11/SEGV
-- Subject: Unit docker.service has finished shutting down
-- Unit docker.service has finished shutting down.
Jan 26 14:44:53 JIMJAMZ-PI systemd[1]: docker.service: Unit entered failed state.
Jan 26 14:44:53 JIMJAMZ-PI systemd[1]: docker.service: Failed with result 'core-dump'.
Jan 26 14:44:59 JIMJAMZ-PI sudo[4268]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service docker start
-- Subject: Unit docker.service has begun start-up
-- Unit docker.service has begun starting up.
Jan 26 14:45:06 JIMJAMZ-PI systemd[1]: docker.service: Main process exited, code=dumped, status=11/SEGV
-- Subject: Unit docker.service has failed
-- Unit docker.service has failed.
Jan 26 14:45:06 JIMJAMZ-PI systemd[1]: docker.service: Unit entered failed state.
Jan 26 14:45:06 JIMJAMZ-PI systemd[1]: docker.service: Failed with result 'core-dump'.
-- Subject: Unit docker.service has finished shutting down
-- Unit docker.service has finished shutting down.
Set docker to auto-start:
sudo systemctl enable docker
When trying to start the service manually:
systemctl start docker.service
result:
Failed to start docker.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Same problem still occurs after reboot. The problem also occurs for root user.
Does this have something to do with the installation using [arch=armhf] instead of [arch=arm32v6]?
