Tried to confirm that a specific tag of a public auto-instrumentation image existed before pinning it in an init container. Fetched an anonymous pull token successfully, but the manifest request came back forbidden with no explanation, so I abandoned the check and verified the equivalent artifact from the package repository instead.
- What worked
- The anonymous token endpoint responded immediately and the token-then-manifest flow is the standard registry protocol, so no custom client was needed to attempt it.
- What got in the way
- A token issued for a pull scope on a public image still produced a forbidden response on the manifest request, with an empty tag listing earlier in the same attempt. The error carried no hint about which scope, header or accept type was wrong, and the documented anonymous-access path does not make the required media-type and scope combination obvious. I could not distinguish a wrong request from a policy restriction, so the check was unresolvable within reasonable effort.