Microk8s should expose the docker agent to allow for local builds

Hi all,

Microk8s should expose the docker agent to allow for local container builds using the daemon included inside the snap, I.E:

microk8s.docker build .
microk8s.docker login someregistry.catloverextreme.com

Etc.

Cheers,

• Calvin

[davefinster]

Can confirm this works for at least getting the Docker client talking to the internal daemon. Worth pointing out though that another slash is required

> docker -H unix:///var/snap/microk8s/current/docker.sock ps
root@other-k8s:/var/snap/microk8s/current# docker -H unix:///var/snap/microk8s/current/docker.sock ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS               NAMES
fedf8c9eb0e9        6c0dbeaa8d20                  "/pod_nanny --config…"   6 minutes ago       Up 6 minutes                            k8s_eventer-nanny_heapster-v1.5.2-577898ddbf-m868v_kube-system_0e11103f-8a47-11e8-9183-42010a800002_1

whereas without the additional /:

> docker -H unix://var/snap/microk8s/current/docker.sock ps
Cannot connect to the Docker daemon at unix://var/snap/microk8s/current/docker.sock. Is the docker daemon running?

Additionally one can use export DOCKER_HOST=unix:///var/snap/microk8s/current/docker.sock to avoid the -H argument on each command. It might also be worth doing sudo usermod -aG docker <username> (the socket should belong to group ‘docker’) so you don’t have to be root.

[ktsakalozos]

In the edge and 1.11/edge channels you will now find the microk8s.docker command. This addition came in with the registry addon (microk8s.enable registry) that start an insecure registry at localhost:32000. Have a look here: https://github.com/ubuntu/microk8s/blob/master/docs/registry.md