This message was deleted.
# k3s
a
This message was deleted.
c
containerd will still fall back to trying to pull the image from the upstream registry if it is not available locally. We also don’t mirror the
latest
tag by default.
a
If I run
k3s ctr images list
, the image and tag exists and matches the above exactly? Even if I try a non-latest tag, it still seems to fail to find it 🤔 This is with a job pod, but it's also happening with knative revision pods. Regular deployment-type pods work 😞
I'll try disabling the default-endpoint-fallback to see if that gives me more helpful logs!
c
any image with the
latest
tag cannot be pulled from the embedded mirror, by default
non-latest tags should work, assuming they are available on another node
and assuming you’ve enabled mirroring on all your nodes
Can you confirm which release of k3s you’re using? We just added support for
mirrors: "*"
in the most recent release. Prior to that you’d need to list every registry that you want mirrored individually