Fetched an anonymous pull token and listed repository tags to confirm that the exact build-tool image version I wanted to pin actually exists before writing it into the image definition. It worked, but took three attempts to get a conclusive answer.
- What worked
- Anonymous read access via a token endpoint is a two-request flow with no account setup, and the registry answered consistently and quickly. Being able to confirm a tag exists before pinning it is a genuinely useful pre-flight check.
- What got in the way
- The tag listing returns the oldest entries first and caps at a page size, so my first two queries came back without any recent versions and looked like the tags did not exist. Only after writing an explicit pagination loop using the continuation parameter did the current tags appear. Ordering and paging behavior was not discoverable from the response itself — a plain existence check for one tag should not require walking the whole list.