I’m trying to get Docker to run on Ubuntu Core 16 but it fails after start. I’ve tried to run through some troubleshooting steps outlined in https://askubuntu.com/questions/907110/docker-snap-cannot-connect-to-the-docker-daemon-is-the-docker-daemon-running-o, but have not had any luck. I’m trying to run this on an ARM device (Compulab IMX7 IOT GATE), and I’m new to Ubuntu Core, so I’m not sure where to get relevant logs.
Any help would be appreciated!
Hi, can you explain more what you mean by it fails to start? Is dockerd not running? What is the output of journalctl -e --no-pager -u snap.docker.dockerd?
Correct, Docker service starts then just shuts down.
Jun 18 19:04:53 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:53.976822500Z” level=debug msg=“Using default logging driver json-file”
Jun 18 19:04:53 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:53.978415875Z” level=debug msg="[graphdriver] trying provided driver: aufs"
Jun 18 19:04:53 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:53.986612500Z” level=debug msg=“processing event stream” module=libcontainerd namespace=plugins.moby
Jun 18 19:04:53 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:53.996011875Z” level=error msg=“AUFS was not found in /proc/filesystems” stor age-driver=aufs
Jun 18 19:04:54 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:54.002554000Z” level=debug msg=“Cleaning up old mountid : start.”
Jun 18 19:04:54 localhost.localdomain docker.dockerd[1640]: Error starting daemo n: error initializing graphdriver: driver not supported
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: M ain process exited, code=exited, status=1/FAILURE
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: U nit entered failed state.
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: F ailed with result ‘exit-code’.
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: S ervice hold-off time over, scheduling restart.
Jun 18 19:04:54 localhost.localdomain systemd[1]: Stopped Service for snap appli cation docker.dockerd.
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: S tart request repeated too quickly.
Jun 18 19:04:54 localhost.localdomain systemd[1]: Failed to start Service for sn ap application docker.dockerd.
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: U nit entered failed state.
Jun 18 19:04:54 localhost.localdomain systemd[1]: snap.docker.dockerd.service: F ailed with result ‘start-limit-hit’.
This seems to be your issue:
Jun 18 19:04:53 localhost.localdomain docker.dockerd[1640]: time=“2019-06-18T19: 04:53.996011875Z” level=error msg=“AUFS was not found in /proc/filesystems” stor age-driver=aufs
What’s the contents of /proc/filesystems?
Also are you able to start dockerd by changing aufs to overlay2 in /var/snap/docker/current/config/daemon.json and restarting dockerd with snap restart docker.dockerd?