https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
w
Are you maybe behind a firewall or proxy?
Can you pull that image with plain docker?
r
I manually pulled image, what should I do next to include that so this error get resolved
I'm in office laptop trying to do local setup using k3d tried everything related to it with the help of chatGPT and claude but couldn't able to resolve. I also tried pull manually that image and apply it to cluster but still same issue, Any help appreciated.
w
Are you maybe behind a firewall or proxy? What version of k3d and K3s are you using?
r
Yes it maybe behind proxy config as it's corporate laptop for security purpose. k3d version v5.8.1 k3s version v1.31.4-k3s1 (default)
w
r
thanks, may i know for this command from where I can find certs.crt and yourcert.crt mentioned below?
Copy code
Mounting the CA Certificate from your host into the node containers at start time via k3d cluster create --volume /path/to/your/certs.crt:/etc/ssl/certs/yourcert.crt
c
those are YOUR certs. They are wherever you find your org’s CA certs.
r
oh got it, is this should be only in /etc/ssl/certs/yourcert.crt path I need to copy? As I don't have root level access on my macbook, but I'm using the helm chart is there way I can do the same there?
w
What helm chart? This is a k3d flag you use when creating the cluster in the first place 👍
r
Copy code
k3d cluster create feature-flag-demo \
  --volume ~/corporate.com.cer:/etc/ssl/certs/corporate-ca.crt \
--registry-config ~/.k3d/registries.yaml
I tried creating cluster with above command but still same issue it's output looks like below
Copy code
WARN[0000] No node filter specified                     
INFO[0000] Prep: Network                                
INFO[0000] Re-using existing network 'k3d-feature-flag-demo' (6b4e9b2a6ce39e13efe4d0a9487e2dda4ff15103d0f9e10350355cb768d394dc) 
INFO[0000] Created image volume k3d-feature-flag-demo-images 
INFO[0000] Starting new tools node...                   
INFO[0000] Starting node 'k3d-feature-flag-demo-tools'  
INFO[0002] Creating node 'k3d-feature-flag-demo-server-0' 
INFO[0002] Creating LoadBalancer 'k3d-feature-flag-demo-serverlb' 
INFO[0002] Using the k3d-tools node to gather environment information 
INFO[0002] Starting new tools node...                   
INFO[0002] Starting node 'k3d-feature-flag-demo-tools'  
INFO[0003] Starting cluster 'feature-flag-demo'         
INFO[0003] Starting servers...                          
INFO[0003] Starting node 'k3d-feature-flag-demo-server-0' 
INFO[0006] All agents already running.                  
INFO[0006] Starting helpers...                          
INFO[0006] Starting node 'k3d-feature-flag-demo-serverlb' 
INFO[0012] Injecting records for hostAliases (incl. host.k3d.internal) and for 3 network members into CoreDNS configmap... 
INFO[0014] Cluster 'feature-flag-demo' created successfully! 
INFO[0014] You can now use it like this:                
kubectl cluster-info
here registries.yaml is
Copy code
mirrors:
  "<http://registry-1.docker.io|registry-1.docker.io>":
    endpoint:
      - "<https://registry-1.docker.io>"
configs:
  "<http://registry-1.docker.io|registry-1.docker.io>":
    tls:
      insecure_skip_verify: true
c
why are you setting docker.io as a mirror for itself
r
I tried without that as well same issue, btw that was suggested by claude.ai
Copy code
configs:
  "<http://registry-1.docker.io|registry-1.docker.io>":
    tls:
      insecure_skip_verify: true
with this config as well same issue
Im able to resolve it, but now another issue came
Copy code
FailedCreatePodSandBox  8s (x5 over 72s)  kubelet            Failed to create pod sandbox: 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 "<http://docker.io/rancher/mirrored-pause:3.6|docker.io/rancher/mirrored-pause:3.6>": failed to resolve reference "<http://docker.io/rancher/mirrored-pause:3.6|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 <http://registry-1.docker.io|registry-1.docker.io>: Try again
107 Views
Open in Slack
PreviousNext
Powered by