<p>I recently got started to learn Kubernetes by using Minikube locally in my Mac. Previously, I was able to start a local Kubernetes cluster with Minikube 0.10.0, created a deployment and viewed Kubernetes dashboard. </p>

<p>Yesterday I tried to delete the cluster and re-did everything from scratch. However, I found I cannot get the assets deployed and cannot view the dashboard. From what I saw, everything seemed to get stuck during container creation. </p>

<p>After I ran <code>minikube start</code>, it reported </p>

<pre><code>Starting local Kubernetes cluster...
Kubectl is now configured to use the cluster.
</code></pre>

<p>When I ran <code>kubectl get pods --all-namespaces</code>, it reported (pay attention to the STATUS column):</p>

<pre><code>kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS              RESTARTS   AGE
kube-system   kube-addon-manager-minikube   0/1       ContainerCreating   0          51s
</code></pre>

<p><code>docker ps</code> showed nothing:</p>

<pre><code>docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
</code></pre>

<p><code>minikube status</code> tells me the VM and cluster are running:</p>

<pre><code>minikubeVM: Running
localkube: Running
</code></pre>

<p>If I tried to create a deployment and an autoscaler, I was told they were created successfully:</p>

<pre><code>kubectl create -f configs
deployment "hello-minikube" created
horizontalpodautoscaler "hello-minikube-autoscaler" created

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                             READY     STATUS              RESTARTS   AGE
default       hello-minikube-661011369-1pgey   0/1       ContainerCreating   0          1m
default       hello-minikube-661011369-91iyw   0/1       ContainerCreating   0          1m
kube-system   kube-addon-manager-minikube      0/1       ContainerCreating   0          21m
</code></pre>

<p>When exposing the service, it said:</p>

<pre><code>$ kubectl expose deployment hello-minikube --type=NodePort
service "hello-minikube" exposed

$ kubectl get service
NAME             CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE
hello-minikube   10.0.0.32    &lt;nodes&gt;       8080/TCP   6s
kubernetes       10.0.0.1     &lt;none&gt;        443/TCP    22m
</code></pre>

<p>When I tried to access the service, I was told:</p>

<pre><code>curl $(minikube service hello-minikube --url)
Waiting, endpoint for service is not ready yet...
</code></pre>

<p><code>docker ps</code> still showed nothing. It looked to me everything got stuck when creating a container. I tried some other ways to work around this issue:</p>

<ol>
<li>Upgraded to minikube 0.11.0</li>
<li>Use the xhyve driver instead of the Virtualbox driver</li>
<li>Delete everything cached, like ~/.minikube, ~/.kube, and the cluster, and re-try</li>
</ol>

<p>None of them worked for me.</p>

<p>Kubernetes is still new to me and I would like to know:</p>

<ol>
<li>How can I troubleshoot this kind of issue? </li>
<li>What could be the cause of this issue?</li>
</ol>

<p>Any help is appreciated. Thanks.</p>

<p>It turned out to be a network problem in my case.</p>
<p>The pod status is &quot;ContainerCreating&quot;, and I found during container creation, docker image will be pulled from gcr.io, which is inaccessible in China (blocked by GFW). Previous time it worked for me because I happened to connect to it via a VPN.</p>
