search

acorn-io / runtime

A simple application deployment framework built on Kubernetes
https://docs.acorn.io/
Apache License 2.0
1.13k stars 101 forks source link

Acorn CLI doesn't respect local machine DNS hosts #1819

Open WoLfulus opened 1 year ago

WoLfulus commented 1 year ago

If MagicDNS of Tailscale (+ override local DNS) is active, Acorn will fail to connect to kubernetes.docker.internal and won't respect the machine hosts overrides Docker Desktop will add to Windows. while Windows terminal still resolves the address to 127.0.0.1, Acorn will insist resolve that to a Tailnet address.

As a workaround, I had to go to ~/.kube/config, duplicate the docker-desktop cluster and change kubernetes.docker.internal to 127.0.0.1 instead, making sure to always use the new cluster when working locally.

I just upgraded to the latest version, and I don't remember having an issue before. I'll give it a try in previous versions just to make sure this is new.

cjellick commented 1 year ago

You mean when the cli is just trying to make calls to the k8s api (like to do acorn run or acorn ps)? If so, that's odd. I believe we are using the same libraries as upstream k8s under the covers.

Let us know what you find trying out older versions.

WoLfulus commented 1 year ago

Yes, whenever it tries to talk to k8s the issue happens. And I'm using the latest one 0.7.1