You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After starting minikube with minikube start --driver docker the environment is stood up however I am unable to ping the minikube ip
~ ping `minikube ip`
PING 192.168.49.2 (192.168.49.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 192.168.49.2 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
In my docker settings I have
I tried to also start minikube with minikube start --driver docker --static-ip 192.168.65.49 and now getting
Preparing Kubernetes v1.30.0 on Docker 26.0.1 ...- E0424 16:16:57.878670 96617 start.go:131] Unable to get host IP: resolve dns to ip: docker exec -t minikube dig +short host.docker.internal: exit status 9
stdout:
;; communications error to 192.168.65.1#53: timed out
;; communications error to 192.168.65.1#53: timed out
;; communications error to 192.168.65.1#53: timed out
;; no servers could be reached
and once minikube is started it shows
~ minikube ip
192.168.65.49
~ ping `minikube ip`
PING 192.168.65.49 (192.168.65.49): 56 data bytes
Request timeout for icmp_seq 0
^C
--- 192.168.65.49 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
On my linux host I am able to ping the minikube ip without issues
What Happened?
After starting minikube with
minikube start --driver docker
the environment is stood up however I am unable to ping theminikube ip
In my docker settings I have
I tried to also start minikube with
minikube start --driver docker --static-ip 192.168.65.49
and now gettingand once minikube is started it shows
On my linux host I am able to ping the
minikube ip
without issuesAttach the log file
with
--static-ip 192.168.65.49
log.txt
without
--static-ip 192.168.65.49
log2.txt
Operating System
macOS (Default)
Driver
Docker
The text was updated successfully, but these errors were encountered: