You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ sudo k3s ctr image pull docker.hxstarrys.me/library/nginx:latestWARN[0000] DEPRECATION: The `configs` property of `[plugins."io.containerd.grpc.v1.cri".registry]` is deprecated since containerd v1.5 and will be removed in containerd v2.0. Use `config_path` instead. docker.hxstarrys.me/library/nginx:latest: resolving |--------------------------------------| elapsed: 30.8s total: 0.0 B (0.0 B/s) INFO[0031] trying next host error="failed to authorize: failed to fetch anonymous token: Get \"https://auth.docker.io/token?scope=repository%3Alibrary%2Fnginx%3Apull&service=registry.docker.io\": dial tcp 66.220.147.11:443: i/o timeout" host=docker.hxstarrys.mectr: failed to resolve reference "docker.hxstarrys.me/library/nginx:latest": failed to authorize: failed to fetch anonymous token: Get "https://auth.docker.io/token?scope=repository%3Alibrary%2Fnginx%3Apull&service=registry.docker.io": dial tcp 66.220.147.11:443: i/o timeout
Containerd is getting access token by accessing auth.docker.io/token instead of docker.hxstarrys.me/v2/auth, and the auth.docker.io is unable to access in China regions.
Reason
Containerd is using different logic to get access token from registry server by accessing https://<REGISTRY>/v2/<REPO>/<IMAGE>/manifests/<TAG> directly instead of accessing https://<REGISTRY>/v2/ first before pulling images.
Description
Unauthorized when pull image using containerd:
Containerd is getting access token by accessing
auth.docker.io/token
instead ofdocker.hxstarrys.me/v2/auth
, and theauth.docker.io
is unable to access in China regions.Reason
Containerd is using different logic to get access token from registry server by accessing
https://<REGISTRY>/v2/<REPO>/<IMAGE>/manifests/<TAG>
directly instead of accessinghttps://<REGISTRY>/v2/
first before pulling images.Workflow logs
The text was updated successfully, but these errors were encountered: