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
uploaded some images (using skaffold, so I guess several "k3d image import")
machine have rebooted, went to suspend a bunch and back
eventually I start get this error whenever trying to deploy new pods that need images from internet: dial tcp: lookup registry-1.docker.io on 127.0.0.11:53: read udp 127.0.0.1:41970->127.0.0.11:53: i/o timeout (this is from events on pod, which is in image pull back-off state)
at the same time resolving docker.io from the host works fine
then I restart cluster by k3d cluster stop mycluster and k3d cluster start mycluster
after that the issue goes away (restarting only coredns does not help unfortunately)
What did you expect to happen
Cluster keeps working as usual, names are resolved ok without the need of cluster restart.
What did you do
How was the cluster created?
k3d cluster create mycluster -p "8000:80@loadbalancer"
What did you do afterwards?
dial tcp: lookup registry-1.docker.io on 127.0.0.11:53: read udp 127.0.0.1:41970->127.0.0.11:53: i/o timeout
(this is from events on pod, which is in image pull back-off state)k3d cluster stop mycluster
andk3d cluster start mycluster
What did you expect to happen
Cluster keeps working as usual, names are resolved ok without the need of cluster restart.
Which OS & Architecture
arch: x86_64
cgroupdriver: cgroupfs
cgroupversion: "1"
endpoint: /var/run/docker.sock
filesystem: extfs
infoname: t480s
name: docker
os: Ubuntu 20.04.1 LTS
ostype: linux
version: 24.0.6
Which version of
k3d
k3d version v5.4.9
k3s version v1.25.7-k3s1 (default)
Which version of docker
The text was updated successfully, but these errors were encountered: