Kubernetes Readiness probe failed error

docker minikube kubernetes-helm
Karan Sodhi picture Karan Sodhi · Jan 31, 2018 · Viewed 29.2k times · Source

While running my container on kubernetes using helm upgrade command, I am getting this error:

'Readiness probe failed: Get http://172.17.0.6:3003/: dial tcp 172.17.0.6:3003: getsockopt: connection refused'.

My docker image is for a node.js application and I am trying to manage it through minikube.

Answer

Dane Jordan picture Dane Jordan · Aug 20, 2018

For anyone else here, if using helm to manage your deployments, you need to set initialDelaySeconds it in the deployments.yaml template in the /templates folder under livenessProbe. The livenessProbe will force restart your pod if the probe cannot connect, as was happening with mine. It wasn't giving my application enough time to build.

Related questions

standard_init_linux.go:211: exec user process caused "exec format error"

I am building the Dockerfile for python script which will run in minikube windows 10 system below is my Dockerfile Building the docker using the below command docker build -t python-helloworld . and loading that in minikube docker demon docker save python-helloworld | (…

Read More
An image does not exist locally with the tag: while pushing image to local registry

I am trying to push an image to a local registry running in minikube but get the below error: Successfully built ee84225eb459 Successfully tagged user/apiserver:0.0.1 $ docker push localhost:5000/user/apiserver:0.0.1 The push refers to a repository [localhost:5000/user/…

Read More
What does minikube docker-env mean?

In the Kubernetes minikube tutorial there is this command to use Minikube Docker daemon : $ eval $(minikube docker-env) What exactly does this command do, that is, what exactly does minikube docker-env mean?

Read More