This message was deleted.
# k3s
a
This message was deleted.
h
is it not using hosts resolv.conf ?
c
i have installed the cluster with the default settings
looks like it is not....
container image registry its able to resolve, just that inside the pod/container there is something wrong
@hundreds-evening-84071 do you know what might have caused the problem?
or @creamy-pencil-82913 can you pls help?
also am working behind a firewall
do i need to do some custom settings for core-dns
?
h
Does your pod contain IP of your core-dns service?
Copy code
kubectl exec --stdin --tty -n <namespace>  <pod> -- cat /etc/resolv.conf
this should match your hosts resolv.conf
Copy code
kubectl exec --stdin --tty -n kube-system <coredns pod> -- cat /etc/resolv.conf
c
Copy code
kubectl exec --stdin --tty -n kube-system coredns-7b98449c4-fndcc -- cat /etc/resolv.conf

error: Internal error occurred: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "b3f5b030f2a9fcc5f88774502671d9167ecba045cfbf1607a9745b5969d52f08": OCI runtime exec failed: exec failed: unable to start container process: exec: "cat": executable file not found in $PATH: unknown
seems cat doesnt work inside cordns pod
btw do you know if service/cluster-cidr matters?
i am using the default ones
Copy code
Cluster CIDR
IPv4/IPv6 network CIDRs to use for pod IPs (default: 10.42.0.0/16).

Service CIDR
IPv4/IPv6 network CIDRs to use for service IPs (default: 10.43.0.0/16).