failed to pull image "rancher/pause:3.1" #939
Replies: 2 comments
-
Hi @teachers-uk-net , thanks for starting this discussion. |
Beta Was this translation helpful? Give feedback.
-
root@vpn-gwd:~# docker exec -it k3d-SSQ1-server-0 ctr --debug image pull docker.io/rancher/pause:3.1 |
Beta Was this translation helpful? Give feedback.
-
Hi
I am new to using k3d although have tested the deployment on a local vm and am now moving to a larger machine in the cloud.
I am using ubuntu 20.04 in an openstack network, when the cluster is created, pods get stuck in ContainerCreating (or Init:0/1)
kubectl get ev --all-namespaces
I can pull images on the command line of the vm e.g. with
docker pull rancher/pause:3.1
andcurl https://registry-1.docker.io/v2/rancher/pause/manifests/3.1
gives me a response, I have tried changing the basic network of docker to see if anything changed, if anyone else knows of why this might be the case please can you help me out?Kind regards
update:
moved on to attempting to use a local registry...
Start the cluster with:
and it still tries to use https://registry-1.docker.io/
add
--registry-config "/home/ubuntu/registries.yaml"
and it fails with:Beta Was this translation helpful? Give feedback.
All reactions