Investigate container registries #16

New Issue

label · 2023-03-14T19:28:21Z

label commented

2023-03-14 19:28:21 +00:00

An announcement was recently made[1] that docker will be ending their free team organizations, which may affect our ability to host our images there. While we currently have images on quay.io and others, we may need to investigate our "primary point" of images, whether that's another registry or self-hosted.

Do we setup our own registry? (eg registry.resf.org)
- What does this entail?
- What is the storage burden?
- Are most of the problems of the past resolved?
Mirroring
- Continue mirroring to quay.io
- Any other mirroring spots? (like ghcr.io aka github)

[1] https://web.docker.com/rs/790-SSB-375/images/privatereposfaq.pdf

An announcement was recently made[1] that docker will be ending their free team organizations, which may affect our ability to host our images there. While we currently have images on quay.io and others, we may need to investigate our "primary point" of images, whether that's another registry or self-hosted. * Do we setup our own registry? (eg registry.resf.org) * What does this entail? * What is the storage burden? * Are most of the problems of the past resolved? * Mirroring * Continue mirroring to quay.io * Any other mirroring spots? (like ghcr.io aka github) [1] https://web.docker.com/rs/790-SSB-375/images/privatereposfaq.pdf

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/meta#16