Microk8s: FAIL: Service snap.microk8s.daemon-containerd is not running

[linxuyalun]

Hi, I'm in China, so I have to set a proxy in microk8s because of the firewall.

I followed the guide to set the proxy.

When I run:

microk8s.kubectl get all --all-namespaces

The following was what I got:

NAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE
kube-system   pod/heapster-v1.5.2-5c5498f57c-tn58j                  0/4     Pending   0          25m
kube-system   pod/kube-dns-6bfbdd666c-r4zgw                         0/3     Pending   0          25m
kube-system   pod/kubernetes-dashboard-6fd7f9c494-p6zrq             0/1     Pending   0          25m
kube-system   pod/monitoring-influxdb-grafana-v4-78777c64c8-rjrcl   0/2     Pending   0          25m

NAMESPACE     NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
default       service/kubernetes             ClusterIP   10.152.183.1    <none>        443/TCP             31m
kube-system   service/heapster               ClusterIP   10.152.183.30   <none>        80/TCP              25m
kube-system   service/kube-dns               ClusterIP   10.152.183.10   <none>        53/UDP,53/TCP       25m
kube-system   service/kubernetes-dashboard   ClusterIP   10.152.183.67   <none>        443/TCP             25m
kube-system   service/monitoring-grafana     ClusterIP   10.152.183.35   <none>        80/TCP              25m
kube-system   service/monitoring-influxdb    ClusterIP   10.152.183.47   <none>        8083/TCP,8086/TCP   25m

NAMESPACE     NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/heapster-v1.5.2                  0/1     1            0           25m
kube-system   deployment.apps/kube-dns                         0/1     1            0           25m
kube-system   deployment.apps/kubernetes-dashboard             0/1     1            0           25m
kube-system   deployment.apps/monitoring-influxdb-grafana-v4   0/1     1            0           25m

NAMESPACE     NAME                                                        DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/heapster-v1.5.2-5c5498f57c                  1         1         0       25m
kube-system   replicaset.apps/kube-dns-6bfbdd666c                         1         1         0       25m
kube-system   replicaset.apps/kubernetes-dashboard-6fd7f9c494             1         1         0       25m
kube-system   replicaset.apps/monitoring-influxdb-grafana-v4-78777c64c8   1         1         0       25m

So I run microk8s.inspect to see what was happening:

 FAIL:  Service snap.microk8s.daemon-containerd is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-containerd
  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

I have no idea what's wrong with it, and here is the report inspection-report-20190330_215859.tar.gz.

[linxuyalun]

I was wondering whether my proxy does not work, so I set the proxy on the terminal, just like:

export http_proxy=http://username:password@${ip-adress:port}
export https_proxy=http://username:password@${ip-adress:port}

Then I curl google.com and I got a response, so I think the proxy server is ok.

[ktsakalozos]

Hi @linxuyalun

Your containerd-env file should be only those two lines:

HTTP_PROXY="YOUR_HTTP_PROXY"
HTTPS_PROXY="YOUR_HTTPS_PROXY"

Remember to restart MicroK8s after you update that file.

[linxuyalun]

It works now! Everything works well so far!

Thank you for your prompt reply!