cannot pull image using crictl

kubernetes-sigs / cri-tools

CLI and validation tools for Kubelet Container Runtime Interface (CRI) .

Apache License 2.0

1.66k stars 450 forks source link

cannot pull image using crictl #1530

Closed XP2600-hub closed 2 months ago

XP2600-hub commented 2 months ago

What happened: I try to pull image using crictl:

crictl pull "docker.io/calico/kube-controllers:v3.25.0"

What you expected to happen: Being able to pull image, machine have internet i can curl any link

How to reproduce it (as minimally and precisely as possible):

crictl pull "docker.io/calico/kube-controllers:v3.25.0"

Anything else we need to know?:

Environment:

Container runtime or hardware configuration: cri-o
OS (e.g: cat /etc/os-release): Ubuntu
Kernel (e.g. uname -a): 6.5.0-45-generic
Others:

SergeyKanzhelev commented 2 months ago

Can you share the following:

Version of CRI-O
Version of crictl
crictl verbose logs
Logs from CRI-O
any mirrors that were configured for docker.io in CRI-O configuration (there are typically mirrors are configured for it)

I don't have CRI-O handy to test, but it works with containerd

kwilczynski commented 2 months ago

Works fine with CRI-O:

INFO[2024-07-25 17:32:26.096806574Z] Pulled image: docker.io/calico/kube-controllers@sha256:095484425365e4eac24abfdd28ba14d133ffcc782c36b5d4f08533ef75ee91e4  file="server/image_pull.go:122" id=1caf1150-2ce2-4d86-93bc-4e453d26bfc4 name=/runtime.v1.ImageService/PullImage

CRI-O version:

crio version Version:        1.31.0
   GitCommit:      59d4b9a3e28986365e9ba0fea1849e5d49cddfdc
   GitCommitDate:  2024-07-25T15:26:19Z
   GitTreeState:   dirty
   BuildDate:      2024-07-25T15:51:53Z
   GoVersion:      go1.22.5
   Compiler:       gc
   Platform:       linux/amd64
   Linkmode:       dynamic
   BuildTags:      
     containers_image_ostree_stub
     apparmor
     containers_image_openpgp
     seccomp
     selinux
     exclude_graphdriver_devicemapper
   LDFlags:          unknown
   SeccompEnabled:   true
   AppArmorEnabled:  true

kwilczynski commented 2 months ago

https://github.com/kubernetes-sigs/cri-tools/issues/1463

saschagrunert commented 2 months ago

I don't think that's an issue with cri-tools, isn't it? Can we close this one then?

XP2600-hub commented 2 months ago

Apologizes seems more like internet issue, strangely docker pull was working on other machine, maybe critools have more strict timeout or something, yes can be closed.