Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify + configure suitable container repository for non-public build images #3711

Closed
sxa opened this issue Aug 14, 2024 · 1 comment
Closed

Comments

@sxa
Copy link
Member

sxa commented Aug 14, 2024

Both Linux/s390x and the new Windows container support use images which we are currently only storing locally on the build hosts instead of in a container registry. This is far from ideal and leaves us with single points of failure.
We should identify a suitable container registry that we authenticate to and push to those during the image creation and pull from the build.
Options:

  • Dockerhub private registry (Subject to any licensing restrictions on those repositories)
  • Azure Container Registry (Potentially best suited for our Windows Azure hosts
  • GitHub container registry (ghcr.io)
  • quay.io
  • Self-hosted?
  • Something else?
    Noting that the OpenJ9 team use a private repository so that is known to work well.
@sxa
Copy link
Member Author

sxa commented Aug 14, 2024

Dup of #3217 which I couldn't find when I was creating this ...

@sxa sxa closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant