<p>I'm doing the kubernetes tutorial locally with minikube on osx. In <a href="https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive/" rel="nofollow noreferrer">https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive/</a> step 3, I get the error</p>

<pre><code>% curl http://localhost:8001/api/v1/namespaces/default/pods/$POD_NAME/proxy/
Error: 'dial tcp 172.17.0.4:8080: getsockopt: connection refused'
Trying to reach: 'http://172.17.0.4:8080/'%
</code></pre>

<p>any idea why this doesn't work locally? the simpler request does work</p>

<pre><code>% curl http://localhost:8001/version
{
  "major": "1",
  "minor": "10",
  "gitVersion": "v1.10.0",
  "gitCommit": "fc32d2f3698e36b93322a3465f63a14e9f0eaead",
  "gitTreeState": "clean",
  "buildDate": "2018-03-26T16:44:10Z",
  "goVersion": "go1.9.3",
  "compiler": "gc",
  "platform": "linux/amd64"
</code></pre>

<p>info</p>

<pre><code>$ kubectl get pods                                          
NAME                                   READY     STATUS             RESTARTS   AGE
kubernetes-bootcamp-74f58d6b87-ntn5r   0/1       ImagePullBackOff   0          21h
</code></pre>

<p>logs</p>

<pre><code>$ kubectl logs $POD_NAME
Error from server (BadRequest): container "kubernetes-bootcamp" in pod "kubernetes-bootcamp-74f58d6b87-w4zh8" is waiting to start: trying and failing to pull image
</code></pre>

<p>so then the run command is starting the node but the pod crashes? why?</p>

<pre><code>$ kubectl run kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1 --port=8080
</code></pre>

<p>I can pull the image without a problem</p>

<pre><code>$ docker pull gcr.io/google-samples/kubernetes-bootcamp:v1
v1: Pulling from google-samples/kubernetes-bootcamp
5c90d4a2d1a8: Pull complete 
ab30c63719b1: Pull complete 
29d0bc1e8c52: Pull complete 
d4fe0dc68927: Pull complete 
dfa9e924f957: Pull complete 
Digest: sha256:0d6b8ee63bb57c5f5b6156f446b3bc3b3c143d233037f3a2f00e279c8fcc64af
Status: Downloaded newer image for gcr.io/google-samples/kubernetes-bootcamp:v1
</code></pre>

<p>describe</p>

<pre><code>$ kubectl describe pods                                      
Name:           kubernetes-bootcamp-74f58d6b87-w4zh8
Namespace:      default
Node:           minikube/10.0.2.15
Start Time:     Tue, 24 Jul 2018 15:05:00 -0400
Labels:         pod-template-hash=3091482643
                run=kubernetes-bootcamp
Annotations:    &lt;none&gt;
Status:         Pending
IP:             172.17.0.3
Controlled By:  ReplicaSet/kubernetes-bootcamp-74f58d6b87
Containers:
  kubernetes-bootcamp:
    Container ID:   
    Image:          gci.io/google-samples/kubernetes-bootcamp:v1
    Image ID:       
    Port:           8080/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:    &lt;none&gt;
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-wp28q (ro)
Conditions:
  Type           Status
  Initialized    True 
  Ready          False 
  PodScheduled   True 
Volumes:
  default-token-wp28q:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-wp28q
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason   Age                 From               Message
  ----     ------   ----                ----               -------
  Normal   BackOff  23m (x281 over 1h)  kubelet, minikube  Back-off pulling image "gci.io/google-samples/kubernetes-bootcamp:v1"
  Warning  Failed   4m (x366 over 1h)   kubelet, minikube  Error: ImagePullBackOff
</code></pre>

<p><a href="https://github.com/kubernetes/minikube" rel="nofollow noreferrer">Minikube</a> is a tool that makes it easy to run <a href="https://kubernetes.io" rel="nofollow noreferrer">Kubernetes</a> locally. </p>

<p>Minikube runs a single-node Kubernetes 
cluster inside a VM on your laptop for users looking to try out Kubernetes or develop with it day-to-day.</p>

<p>Back to your issue. Have you checked if you provided enough resources to run Minikube environment?</p>

<p>You may try to run minikube and force allocate more memory:</p>

<pre><code>minikube start --memory 4096
</code></pre>

<p>For further analysis, please provide information about resources dedicated to this installation and
type of hypervisor you use.</p>
