minikube error trying to reach 172.17.0.4:8080 on osx

Minikube is a tool that makes it easy to run Kubernetes locally.

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.

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

You may try to run minikube and force allocate more memory:

minikube start --memory 4096

For further analysis, please provide information about resources dedicated to this installation andtype of hypervisor you use.

Sounds like a networking issue. Your VM is unable to pull the images from gcr.io:443.

Here's what your kubectl describe pods kubernetes-bootcamp-xxx should looks like:

  Type    Reason                 Age   From               Message  ----    ------                 ----  ----               -------  Normal  Scheduled              5m    default-scheduler  Successfully assigned kubernetes-bootcamp-5c69669756-xbbmn to minikube  Normal  SuccessfulMountVolume  5m    kubelet, minikube  MountVolume.SetUp succeeded for volume "default-token-cfq65"  Normal  Pulling                5m    kubelet, minikube  pulling image "gcr.io/google-samples/kubernetes-bootcamp:v1"  Normal  Pulled                 5m    kubelet, minikube  Successfully pulled image "gcr.io/google-samples/kubernetes-bootcamp:v1"  Normal  Created                5m    kubelet, minikube  Created container  Normal  Started                5m    kubelet, minikube  Started container  Normal  SuccessfulMountVolume  1m    kubelet, minikube  MountVolume.SetUp succeeded for volume "default-token-cfq65"  Normal  SandboxChanged         1m    kubelet, minikube  Pod sandbox changed, it will be killed and re-created.  Normal  Pulled                 1m    kubelet, minikube  Container image "gcr.io/google-samples/kubernetes-bootcamp:v1" already present on machine  Normal  Created                1m    kubelet, minikube  Created container  Normal  Started                1m    kubelet, minikube  Started container

Try this from your host, to narrow down if it's a networking issue with your VM or your host machine:

$ docker pull gcr.io/google-samples/kubernetes-bootcamp:v1v1: Pulling from google-samples/kubernetes-bootcamp5c90d4a2d1a8: Pull completeab30c63719b1: Pull complete29d0bc1e8c52: Pull completed4fe0dc68927: Pull completedfa9e924f957: Pull completeDigest: sha256:0d6b8ee63bb57c5f5b6156f446b3bc3b3c143d233037f3a2f00e279c8fcc64afStatus: Downloaded newer image for gcr.io/google-samples/kubernetes-bootcamp:v1