Closed mcandre closed 3 years ago
hi @mcandre thank you for reaching out,
host.minikube.internal
is meant to be used for accesing the user's machine from inside the container (found some doc on our site on it https://minikube.sigs.k8s.io/docs/handbook/host-access/ )
are you asking, you want on your own machine (your own laptop) host.minikube.internal
should resolve to minikube ip
?
have you considered using
something like
minikube ip -p cluster1
minikube ip -p cluster2
to get the minikube IP ?
and what OS and what driver of minikube do u use?
/triage needs-information
Hi @mcandre, we haven't heard back from you, do you still have this issue? There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.
I will close this issue for now but feel free to reopen when you feel ready to provide more information.
I am having trouble getting
host.minikube.internal
to resolve on my Mac host. It only seems to resolve correctly within containers, which unfortunately makes it a lot harder to developer frontend applications. Particularly when redirects are involved between multiple minikube containers.Please make sure that the
host.minikube.internal
domain can resolve from the perspective of the host. So that frontend applications with redirects between containers will be able to intuitively work.Steps to reproduce the issue:
minikube start
Full output of
minikube logs
command:Full output of failed command: