Is there a way to use host docker like Minikube `eval $(minikube docker-env -u)`

Is there a way to switch microk8s to use the docker host for images? I have read https://github.com/ubuntu/microk8s/issues/287 and https://github.com/ubuntu/microk8s/blob/master/docs/registry.md

and cannot see how to do this. Minikube’s eval command is simple easy way to switch I am looking for something similar.

Running ‘docker -H unix:///var/snap/microk8s/current/docker.sock ps’ does not seem to have any effect for me.

Please run microk8s.inspect and attach the generated tarball to this issue.

$ microk8s.inspect
Inspecting services
  Service snap.microk8s.daemon-docker is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system info
  Copy network configuration to the final report tarball
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Inspect kubernetes cluster

Building the report tarball
  Report tarball is at /var/snap/microk8s/412/inspection-report-20190306_230601.tar.gz

We appreciate your feedback. Thank you for using microk8s.

[melissapalmer]

Thank You, @ktsakalozos I have managed to sort out using your recommendation of tagging an image and the pushing it to the registry used by MicroK8s:

The following commands are what I used, and am happy with this it allows me to only build the docker image once.

microk8s.enable registry
docker build -t org.myorg/myimage .
docker tag org.myorg/myimage localhost:32000/org.myorg/myimage
docker push localhost:32000/org.myorg/myimage
helm install --name mychart --set image.repository=localhost:32000/org.myorg/myimage  helm-chart/mychart

[waquidvp]

As https://github.com/ubuntu/microk8s/issues/287 mentioned, especially with the move to containerd now happening, your best option to stay future proof would be to build locally and use the registry. Eventually microk8s.docker won’t be available anymore to run the microk8s.docker build command.