Minikube registry addon fails

[MrBuddyCasino]

I can't pull images from the Minikube registry using localhost:5000/instana/echo-client, it fails with "no route to host". Pushing works though!

The exact command to reproduce the issue:

minikube start --insecure-registry "10.0.0.0/24" --container-runtime=cri-o
minikube addons enable registry
docker run --name socat-bridge --rm -it --network=host alpine ash -c "apk add socat && socat TCP-LISTEN:5000,reuseaddr,fork TCP:$(minikube ip):5000" &>/dev/null &

# build & push image
docker build -t instana/echo-client .
docker tag instana/echo-client localhost:5000/instana/echo-client
docker push localhost:5000/instana/echo-client

kubectl apply -f client.yaml

The full output of the command that failed:

Successfully assigned default/echo-client-hlxnk to minikube
Pulling image "localhost:5000/instana/echo-client"
Failed to pull image "localhost:5000/instana/echo-client": rpc error: code = Unknown desc = pinging docker registry returned: Get http://localhost:5000/v2/: dial tcp 127.0.0.1:5000: connect: no route to host
Error: ErrImagePull

The output of the minikube logs command:

see minikube.log

The operating system version: macOS Mojave

[MrBuddyCasino]

I also tried using registry.kube-system.svc.cluster.local:80/instana/echo-client as the container image location, but the host lookup failed with ErrImagePull: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.kube-system.svc.cluster.local:80/v2/: dial tcp: lookup registry.kube-system.svc.cluster.local: no such host.

Using the IP worked tough: 10.111.155.225:80/instana/echo-client

[MrBuddyCasino]

This might be a duplicate of
#4553
#4547

[medyagh]

@MrBuddyCasino I am curious, do you have this issue with other runtimes other than cri-o ?

and also do you mind minikube stop and start after enabling the addon ?

[medyagh]

I will close this issue to track it here #6024