This message was deleted.
# k3sa
adamant-kite-43734
03/03/2025, 8:27 AMThis message was deleted.
c
crooked-oyster-59582
03/03/2025, 9:40 AMcontainerd log shows failed interaction with registry-1.docker.io but I imported the image locally with 'ctr image import'. The image metadata must be an issue
s
sticky-summer-13450
03/03/2025, 11:48 AMIt doesn't look like you imported the images into the correct namespace.
i.e.
ctr -n=<http://k8s.io|k8s.io> image import ...c
crooked-oyster-59582
03/03/2025, 12:47 PMI found no difference with k8s.io as namespace, but have started using it consistently
g
gentle-engine-82305
03/03/2025, 12:50 PMdid you look at this? https://github.com/k3s-io/k3s/issues/7015
gentle-engine-82305
03/03/2025, 12:51 PManyway why don't you deploy a local registry and push images to it?
c
crooked-oyster-59582
03/03/2025, 1:35 PM@gentle-engine-82305 thank you - that error is very similar but not the same. I tried a local docker registry but I would prefer to not install docker at all.
crooked-oyster-59582
03/03/2025, 2:14 PM"pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed"
crooked-oyster-59582
03/03/2025, 2:18 PMcontainerd logs show
Copy code
time="2025-03-03T09:15:22.739740698-05:00" level=info msg="fetch failed" error="pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed" host=registry-1.docker.io8 Views