Microk8s: No node created when installing microk8s

[markmandel]

Install microk8s, and unfortunately there was no Nodes inside the cluster, and therefore no Pods could be started.

When running:

$ microk8s.kubectl get nodes
No resources found.

Also when running

$  microk8s.kubectl get nodes
No resources found.

All Pods failed with the message: Warning FailedScheduling 6s (x37 over 10m) default-scheduler no nodes available to schedule pods

As per this article, I stopped Docker and reinstalled the snap, and started it again, but that did not solve the issue.

You can see the video of my attempt on Twitch for next 14 days, so you can see all the steps and workarounds I took.

I'll add the Youtube version when it's uploaded, so it's here forever.

---

OS: Debian, Stretch

Docker Version:
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24
Built: Wed Mar 21 23:10:06 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm

Server:
Engine:
Version: 18.03.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.4
Git commit: 0520e24
Built: Wed Mar 21 23:08:35 2018
OS/Arch: linux/amd64
Experimental: false

[marcoceppi]

A couple of things, which I don't think we make clear (and will need updating). The reason for the Docker conflict is that this snap installs it's own, separate, Docker. We're working to make it so a host version Docker doesn't conflict. As such, you'll want to keep your docker daemon off during the use of microk8s.

I've never used microk8s on Debian Stretch, but I gave it a try in GCP with a fresh stretch instance and recorded the process. The first time it worked, the second time it didn't (but with different problems). We've got some inconsistencies we need to look into.

The output of the following would be helpful:

snap info microk8s
journalctl -u snap.microk8s.daemon-kubelet.service

[ktsakalozos]

Hi @markmandel ,

Thank you for taking the time to try out microk8s. I am deeply sorry it did not work.

Microk8s will start all kubernetes services in your system. The fact that you do not see nodes with microk8s.kubectl get no means that the node services failed to start. The services we are interested in are kubelet, docker and kubeproxy.

Can you please check that these three services are running?

sudo systemctl status snap.microk8s.daemon-docker
sudo systemctl status snap.microk8s.daemon-proxy
sudo systemctl status snap.microk8s.daemon-kubelet

For the services that are not running would it be possible to share the output of journalctl -u eg:

sudo journalctl -u snap.microk8s.daemon-kubelet

Regardless what the problem turns out to be your video is very instructive. It shows what a user would try to check when he finds a problem. We need to improve documentation and the microk8s bootstrap process.

Also the arguments the services start with are under /var/snap/microk8s/currect/args/* . You will need to edit those files and restart the respective kubernetes service. Another point to include in the docs.

Thank you again for opening this issue. I am going to try to reproduce it in in your Debian distribution.

[marcoceppi]

To add to this, I found something interesting I have not seen before when using snaps. It appears the snap wasn't fully installed on the first attempt.

https://asciinema.org/a/KM8tlQ0B1ZlukIrHKJmdLOAVS

I did two attempts, that being the second one. While the first one worked without issue (but the recording got messed up) this one resulted in a majority of services not working until after a complete remove and install of the snap. While these two issues are likely not linked, it is something to be aware of.

I was able to get microk8s working on Debian, but I think this reinforces the need of a microk8s.status command to do self introspection. I'll create an issue to start tracking that idea.

[markmandel]

Thanks for the quick responses, and looking forward to getting this all fixed - let me know how else I can help!

So I ran sudo service docker stop to shut down docker.

I then ran sudo snap install microk8s --beta --classic to install microk8s, and haven't turned docker back on.

Not sure if this is relevant or not, but after installing microk8s, I still wasn't able to connect to the Docker daemon.

$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I also threw all the requested logs and status info into this gist for your review.

Please let me know if you require any more information!

[marcoceppi]

It looks like the docker bundled in microk8s isn't working, it's not running in your output and it's what kubelet is complaining about it. Could you provide this log as well?

journalctl -u snap.microk8s.daemon-docker.service

This should pin-point the issue.

[markmandel]

$ journalctl -u snap.microk8s.daemon-docker.service

-- Logs begin at Thu 2018-05-31 09:05:34 PDT, end at Thu 2018-05-31 13:10:12 PDT. --
May 31 09:10:10 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:10:10 markmandel microk8s.daemon-docker[6018]: Using a docker-default template
May 31 09:10:11 markmandel microk8s.daemon-docker[6018]: Reloading AppArmor profiles
May 31 09:10:14 markmandel microk8s.daemon-docker[6018]: AppArmor patched
May 31 09:10:18 markmandel microk8s.daemon-docker[6018]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:10:18 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:10:18 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:18 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:10:18 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:10:18 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:10:18 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:10:18 markmandel microk8s.daemon-docker[6213]: Docker default profile already patched
May 31 09:10:19 markmandel microk8s.daemon-docker[6213]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:10:19 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel microk8s.daemon-docker[6229]: Docker default profile already patched
May 31 09:10:19 markmandel microk8s.daemon-docker[6229]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:10:19 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel microk8s.daemon-docker[6244]: Docker default profile already patched
May 31 09:10:19 markmandel microk8s.daemon-docker[6244]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:10:19 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel microk8s.daemon-docker[6260]: Docker default profile already patched
May 31 09:10:19 markmandel microk8s.daemon-docker[6260]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:10:19 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 09:10:19 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:10:19 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:29 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:23:30 markmandel microk8s.daemon-docker[12075]: Docker default profile already patched
May 31 09:23:35 markmandel microk8s.daemon-docker[12075]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:23:35 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:23:35 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:35 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:23:36 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel microk8s.daemon-docker[12197]: Docker default profile already patched
May 31 09:23:36 markmandel microk8s.daemon-docker[12197]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:23:36 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel microk8s.daemon-docker[12213]: Docker default profile already patched
May 31 09:23:36 markmandel microk8s.daemon-docker[12213]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:23:36 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel microk8s.daemon-docker[12229]: Docker default profile already patched
May 31 09:23:36 markmandel microk8s.daemon-docker[12229]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:23:36 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:23:36 markmandel microk8s.daemon-docker[12245]: Docker default profile already patched
May 31 09:23:36 markmandel microk8s.daemon-docker[12245]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:36 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:23:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:23:37 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:23:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 09:23:37 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 09:23:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:23:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:02 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:27:02 markmandel microk8s.daemon-docker[14394]: Docker default profile already patched
May 31 09:27:08 markmandel microk8s.daemon-docker[14394]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:27:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel microk8s.daemon-docker[14549]: Docker default profile already patched
May 31 09:27:08 markmandel microk8s.daemon-docker[14549]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:27:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel microk8s.daemon-docker[14593]: Docker default profile already patched
May 31 09:27:08 markmandel microk8s.daemon-docker[14593]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:27:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel microk8s.daemon-docker[14612]: Docker default profile already patched
May 31 09:27:08 markmandel microk8s.daemon-docker[14612]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:27:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:27:08 markmandel microk8s.daemon-docker[14627]: Docker default profile already patched
May 31 09:27:08 markmandel microk8s.daemon-docker[14627]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:27:09 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 09:27:09 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:27:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:14 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel microk8s.daemon-docker[15798]: Docker default profile already patched
May 31 09:28:14 markmandel microk8s.daemon-docker[15798]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:28:14 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel microk8s.daemon-docker[15934]: Docker default profile already patched
May 31 09:28:14 markmandel microk8s.daemon-docker[15934]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:28:14 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel microk8s.daemon-docker[15951]: Docker default profile already patched
May 31 09:28:14 markmandel microk8s.daemon-docker[15951]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:28:14 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:28:14 markmandel microk8s.daemon-docker[16009]: Docker default profile already patched
May 31 09:28:14 markmandel microk8s.daemon-docker[16009]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:14 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:28:15 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:28:15 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 09:28:15 markmandel microk8s.daemon-docker[16030]: Docker default profile already patched
May 31 09:28:15 markmandel microk8s.daemon-docker[16030]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 09:28:15 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 09:28:15 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 09:28:15 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:33 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 10:51:34 markmandel microk8s.daemon-docker[39675]: Docker default profile already patched
May 31 10:51:39 markmandel microk8s.daemon-docker[39675]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 10:51:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel microk8s.daemon-docker[39773]: Docker default profile already patched
May 31 10:51:39 markmandel microk8s.daemon-docker[39773]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 10:51:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel microk8s.daemon-docker[39790]: Docker default profile already patched
May 31 10:51:39 markmandel microk8s.daemon-docker[39790]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 10:51:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel microk8s.daemon-docker[39856]: Docker default profile already patched
May 31 10:51:39 markmandel microk8s.daemon-docker[39856]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 10:51:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 10:51:39 markmandel microk8s.daemon-docker[39873]: Docker default profile already patched
May 31 10:51:39 markmandel microk8s.daemon-docker[39873]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 10:51:40 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 10:51:40 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 10:51:40 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 10:51:40 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 10:51:40 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 10:51:40 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:02 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 11:13:02 markmandel microk8s.daemon-docker[46465]: Docker default profile already patched
May 31 11:13:08 markmandel microk8s.daemon-docker[46465]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 11:13:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 11:13:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 11:13:08 markmandel microk8s.daemon-docker[46578]: Docker default profile already patched
May 31 11:13:08 markmandel microk8s.daemon-docker[46578]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 11:13:08 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 11:13:08 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 11:13:08 markmandel microk8s.daemon-docker[46622]: Docker default profile already patched
May 31 11:13:08 markmandel microk8s.daemon-docker[46622]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:08 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 11:13:09 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel microk8s.daemon-docker[46638]: Docker default profile already patched
May 31 11:13:09 markmandel microk8s.daemon-docker[46638]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 11:13:09 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel microk8s.daemon-docker[46654]: Docker default profile already patched
May 31 11:13:09 markmandel microk8s.daemon-docker[46654]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 11:13:09 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 11:13:09 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 11:13:09 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:32 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 12:41:32 markmandel microk8s.daemon-docker[50700]: Docker default profile already patched
May 31 12:41:37 markmandel microk8s.daemon-docker[50700]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 12:41:37 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 12:41:37 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 12:41:37 markmandel microk8s.daemon-docker[50773]: Docker default profile already patched
May 31 12:41:37 markmandel microk8s.daemon-docker[50773]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:37 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 12:41:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel microk8s.daemon-docker[50792]: Docker default profile already patched
May 31 12:41:38 markmandel microk8s.daemon-docker[50792]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 12:41:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel microk8s.daemon-docker[50815]: Docker default profile already patched
May 31 12:41:38 markmandel microk8s.daemon-docker[50815]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 12:41:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel microk8s.daemon-docker[50842]: Docker default profile already patched
May 31 12:41:38 markmandel microk8s.daemon-docker[50842]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 12:41:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 12:41:38 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 12:41:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:33 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 13:08:33 markmandel microk8s.daemon-docker[60478]: Docker default profile already patched
May 31 13:08:38 markmandel microk8s.daemon-docker[60478]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 13:08:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 13:08:38 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 13:08:38 markmandel microk8s.daemon-docker[60582]: Docker default profile already patched
May 31 13:08:38 markmandel microk8s.daemon-docker[60582]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 13:08:38 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 13:08:38 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 13:08:38 markmandel microk8s.daemon-docker[60628]: Docker default profile already patched
May 31 13:08:38 markmandel microk8s.daemon-docker[60628]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:38 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 13:08:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel microk8s.daemon-docker[60677]: Docker default profile already patched
May 31 13:08:39 markmandel microk8s.daemon-docker[60677]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 13:08:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel systemd[1]: Started Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel microk8s.daemon-docker[60703]: Docker default profile already patched
May 31 13:08:39 markmandel microk8s.daemon-docker[60703]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: data-root
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Main process exited, code=exited, status=1/FAILURE
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Service hold-off time over, scheduling restart.
May 31 13:08:39 markmandel systemd[1]: Stopped Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Start request repeated too quickly.
May 31 13:08:39 markmandel systemd[1]: Failed to start Service for snap application microk8s.daemon-docker.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Unit entered failed state.
May 31 13:08:39 markmandel systemd[1]: snap.microk8s.daemon-docker.service: Failed with result 'exit-code'.

[marcoceppi]

What is in the /etc/docker/daemon.json file on your root? (sans any private information)

[markmandel]

sudo cat /etc/docker/daemon.json
[sudo] password for markmandel:
{
  "data-root": "/usr/local/google/docker",
  "bip": "192.168.9.1/24",
  "storage-driver": "overlay2",
  "debug": true,
  "registry-mirrors": ["https://mirror.gcr.io"]
}

[ktsakalozos]

The docker logs were very helpful. snap.microk8s.daemon-docker.service attempts to get its configuration from the default location /etc/docker/daemon.json this results in reading the config parameters of the already installed dockerd. It complains that the data-root is not known since this config argument replaced the graph parameter.

The quick fix is to not use the /etc/docker/daemon.json:

sudo sh -c "echo '{}' > /var/snap/microk8s/common/daemon.json"
sudo sh -c "echo '--config-file=\$SNAP_COMMON/daemon.json' >> /var/snap/microk8s/55/args/dockerd"
sudo systemctl restart snap.microk8s.daemon-docker.service
sudo systemctl restart snap.microk8s.daemon-kubelet.service

We will soon have this fix on edge, PR is on its way. Ultimately, this will be handles when we move all services to strict confinement.

[markmandel]

Thanks - I'll give it a shot when the new release comes out!

If you are willing, I'm super curious as to why you ship your own docker daemon etc and don't use the one that is already in the system? (I'm sure you have good reasons, just curious)

[ktsakalozos]

The fix is released in edge and will hit beta soon.

We ship our own docker because of how snaps are supposed to work. Snaps pack the entire software stack they will need so that they can be deployed on any distribution and release. Its like docker containers, they package everything needed by the application and they run everywhere. If we tried to reuse the dockerd installed (if any) we would have to deal with whichever docker version the user has available.

[ktsakalozos]

The fix is in beta now. I am closing this. Please reopen if you see this appearing again.

Thank you for reporting this.