This message was deleted.
# k3da
adamant-kite-43734
03/11/2023, 12:59 PMThis message was deleted.
w
wide-garage-9465
03/11/2023, 1:11 PMDo you have any logs from the server container?
h
handsome-salesclerk-54324
03/11/2023, 1:14 PMHow do I get these?
w
wide-garage-9465
03/11/2023, 1:15 PMdocker logs k3d-<cluster name>-server-0h
handsome-salesclerk-54324
03/11/2023, 1:17 PMThanks its showing
E0311 131622.351577 8 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"helm-install-traefik-crd-ncwc2_kube-system(ae36e368-d021-4e11-b9fd-57e7fdb788aa)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"helm-install-traefik-crd-ncwc2_kube-system(ae36e368-d021-4e11-b9fd-57e7fdb788aa)\\\": rpc error: code = Unknown desc = failed to get sandbox image \\\"rancher/mirrored-pause:3.6\\\": failed to pull image \\\"rancher/mirrored-pause:3.6\\\": failed to pull and unpack image \\\"docker.io/rancher/mirrored-pause:3.6\\\": failed to resolve reference \\\"docker.io/rancher/mirrored-pause:3.6\\\": failed to do request: Head \\\"https://registry-1.docker.io/v2/rancher/mirrored-pause/manifests/3.6\\\": dial tcp: lookup registry-1.docker.io on 127.0.0.1153 read udp 127.0.0.138427 >127.0.0.1153: i/o timeout\"" pod="kube-system/helm-install-traefik-crd-ncwc2" podUID=ae36e368-d021-4e11-b9fd-57e7fdb788aa
w
wide-garage-9465
03/11/2023, 1:32 PMSome networking/DNS issue?
Are you in a different network or enabled VON maybe?
h
handsome-salesclerk-54324
03/11/2023, 2:12 PMI am able to fetch and run images from docker e.g.
docker run -d -p 8081:80 docker/getting-startedworks However this fails
wget https://registry-1.docker.io/v2/rancher/mirrored-pause/manifests/3.6
--2023-03-11 060921-- https://registry-1.docker.io/v2/rancher/mirrored-pause/manifests/3.6
Resolving registry-1.docker.io (registry-1.docker.io)... 34.205.13.154, 44.205.64.79, 3.216.34.172
Connecting to registry-1.docker.io (registry-1.docker.io)|34.205.13.154|:443... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Username/Password Authentication Failed.
handsome-salesclerk-54324
03/12/2023, 12:51 AMThis also works:
k3d cluster create local-k8sINFO[0000] Prep: NetworkINFO[0000] Re-using existing network 'k3d-local-k8s' (f300436aff034ab53bb5e632dcdb4c4dae62549ea1f0c94efa493032cef91161)INFO[0000] Created image volume k3d-local-k8s-imagesINFO[0000] Starting new tools node...INFO[0000] Pulling image '<http://ghcr.io/k3d-io/k3d-tools:5.4.8|ghcr.io/k3d-io/k3d-tools:5.4.8>'INFO[0001] Creating node 'k3d-local-k8s-server-0'INFO[0002] Pulling image '<http://docker.io/rancher/k3s:v1.25.6-k3s1|docker.io/rancher/k3s:v1.25.6-k3s1>'INFO[0002] Starting Node 'k3d-local-k8s-tools'INFO[0009] Creating LoadBalancer 'k3d-local-k8s-serverlb'INFO[0010] Pulling image '<http://ghcr.io/k3d-io/k3d-proxy:5.4.8|ghcr.io/k3d-io/k3d-proxy:5.4.8>'INFO[0013] Using the k3d-tools node to gather environment informationINFO[0014] HostIP: using network gateway 172.22.0.1 addressINFO[0014] Starting cluster 'local-k8s'INFO[0014] Starting servers...INFO[0014] Starting Node 'k3d-local-k8s-server-0'INFO[0018] All agents already running.INFO[0018] Starting helpers...INFO[0018] Starting Node 'k3d-local-k8s-serverlb'INFO[0025] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...INFO[0027] Cluster 'local-k8s' created successfully!INFO[0027] You can now use it like this:kubectl cluster-infow
wide-garage-9465
03/21/2023, 8:16 AMHey 👋
Is this actually still an issue?
143 Views