The service running on your host must either be bound to all IP’s (0.0.0.0) and interfaces, or to the IP and interface your VM is bridged against. If the service is bound only to localhost (127.0.0.1), this will not work.
To make it easier to access your host, minikube v1.10 adds a hostname entry
/etc/hosts. The IP which
host.minikube.internal resolves to is different across drivers, and may be different across clusters.
You can use
minikube ssh to confirm connectivity:
_ _ _ _ ( ) ( ) ___ ___ (_) ___ (_)| |/') _ _ | |_ __ /' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\ | ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/ (_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____) $ ping host.minikube.internal PING host.minikube.internal (192.168.64.1): 56 data bytes 64 bytes from 192.168.64.1: seq=0 ttl=64 time=0.225 ms
To test connectivity to a specific TCP service listening on your host, use
nc -vz host.minikube.internal <port>:
$ nc -vz host.minikube.internal 8000 Connection to host.minikube.internal 8000 port [tcp/*] succeeded!
Here are how to interpret the different messages:
Connection succeeded: You are connected!
Connection refused: the service is not listening on the port, at least not across all interfaces
When using an older version of minikube, you may have to manually install tools like
netcat within the minikube image:
sudo apt install iputils-ping netcat-openbsd
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.