Mirror registry is not working during bootstrap #8094
Replies: 3 comments 7 replies
-
|
using "talosctl dmesg | grep hub" will show talos try to search my domains in 1.1.1.1, which certainly get no answer, according to containerd/docs/hosts.md when hosts(mirror) of a server all fails, it will fall back to server url. so in the end it seems to be above error. correct me if I am wrong. relative logs below talosctl dmesg | grep retrying
172.19.82.31: user: warning: [2023-12-20T03:37:30.55778073Z]: [talos] retrying error: failed to pull image "ghcr.io/siderolabs/kubelet:v1.29.0": failed to resolve reference "ghcr.io/siderolabs/kubelet:v1.29.0": failed to do request: Head "https://hub.homelab.internal/ghcr.io/siderolabs/kubelet/manifests/v1.29.0?ns=ghcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
172.19.82.31: user: warning: [2023-12-20T03:37:30.55974773Z]: [talos] retrying error: failed to pull image "gcr.io/etcd-development/etcd:v3.5.11": failed to resolve reference "gcr.io/etcd-development/etcd:v3.5.11": failed to do request: Head "https://hub.homelab.internal/gcr.io/etcd-development/etcd/manifests/v3.5.11?ns=gcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
talosctl dmesg | grep hub
172.19.82.31: kern: info: [2023-12-20T03:37:19.356164497Z]: usbcore: registered new interface driver hub
172.19.82.31: user: warning: [2023-12-20T03:37:30.644291497Z]: [talos] retrying error: failed to pull image "ghcr.io/siderolabs/kubelet:v1.29.0": failed to resolve reference "ghcr.io/siderolabs/kubelet:v1.29.0": failed to do request: Head "https://hub.homelab.internal/ghcr.io/siderolabs/kubelet/manifests/v1.29.0?ns=ghcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
172.19.82.31: user: warning: [2023-12-20T03:37:30.646258497Z]: [talos] retrying error: failed to pull image "gcr.io/etcd-development/etcd:v3.5.11": failed to resolve reference "gcr.io/etcd-development/etcd:v3.5.11": failed to do request: Head "https://hub.homelab.internal/gcr.io/etcd-development/etcd/manifests/v3.5.11?ns=gcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
172.19.82.31: user: warning: [2023-12-20T03:37:35.948464497Z]: failed to pull image "ghcr.io/siderolabs/kubelet:v1.29.0": failed to resolve reference "ghcr.io/siderolabs/kubelet:v1.29.0": failed to do request: Head "https://hub.homelab.internal/ghcr.io/siderolabs/kubelet/manifests/v1.29.0?ns=ghcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
172.19.82.31: user: warning: [2023-12-20T03:37:35.954358497Z]: failed to pull image "gcr.io/etcd-development/etcd:v3.5.11": failed to resolve reference "gcr.io/etcd-development/etcd:v3.5.11": failed to do request: Head "https://hub.homelab.internal/gcr.io/etcd-development/etcd/manifests/v3.5.11?ns=gcr.io": dial tcp: lookup hub.homelab.internal on 1.1.1.1:53: no such host
|
Beta Was this translation helpful? Give feedback.
-
|
@smira I have migrated my question from previous issue, and provide more info, please help me |
Beta Was this translation helpful? Give feedback.
-
|
After a few retries, the solution seems clear.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When I start a new talos cluster with private registry, it shows
"failed to pull image "gcr.io/etcd-development/etcd:v3.5.11": failed to resolve reference "gcr.io/etcd-development/etcd:v3.5.11": gcr.io/etcd-development/etcd:v3.5.11: not found",
however if I change the etcd image to "hub.homelab.internal/gcr.io/etcd-development/etcd:v3.5.11", it is working.
To reproduce my scenario, I will provide necessary snipplets below:
Beta Was this translation helpful? Give feedback.
All reactions