Adoptium build_images on ghcr.io needs to have public access
Summary
Discussed briefly with @fgurr last week, but raising this to formalise the requirement. We have automation for pushing some of the images we use for building Temurin up to ghcr as an alternative to dockerhub as per https://github.com/adoptium/infrastructure/issues/3830 - the original token access request was this was under https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5664 (confidential)
At the moment we have two packages under github.com/adoptium/packages - one is test-containers, which is public. The second is our new one build_images which is currently listed as "internal" which means it is not publicly accessible.
I'd like build_images publicly accessible so they can be used without requiring an authentication token. FYI @abrousseaue0s
Steps to reproduce
Try to pull the image: docker pull ghcr.io/adoptium/adoptium_build_image:centos7_linux-amd64
What is the current bug behavior?
Error response from daemon: Head "https://ghcr.io/v2/adoptium/adoptium_build_image/manifests/latest": denied: denied
What is the expected correct behavior?
Image is pulled down successfully without requiring authentication (It works with authentication as can be seen in https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/637/console)
Relevant logs and/or screenshots
The above snippets should provide enough clarity :-)
Priority
- Urgent
- High
- Medium
- Low
Severity
- Blocker
- Major
- Normal
- Low
Impact
There are timescales with Adam Brousseau's team are under to migrate away from dockerhub and they are looking to test this as soon as practical.