This message was deleted.
# k3d
a
This message was deleted.
w
You need to set
K3D_FIX_DNS=1
if you have issues with DNS in the k3d cluster, yep.
l
I, too, could not get DNS to work inside container for k3d. Tried the above and other ways, none worked thus far.
I used this one when creating cluster
k3d cluster create --network host
, and after updating docker’s daemon.json and restarting it, finally it works:
K3D_FIX_DNS
won’t work in this case.
Copy code
{
   "bip": ...,
   "dns": ["dns_ip1"],
   "dns-search": ["<http://mydomain.com|mydomain.com>"]
}
w
@little-dress-13576 you're talking about DNS in the K3s container or in a pod inside the K3s cluster?
l
in a pod inside the k3s cluster
w
I don't think
K3D_FIX_DNS
will do anything with
--network=host
🤔
h
It would be helpful if the k3d official docs discussed this and related DNS topics/issues, I could find no mention of this on https://k3d.io/