Choosing an Alternative to GitHub Package Registry for Docker Images Due to IPv6 Limitations

[NgLoader]

Problem

GitHub Container Registry (ghcr.io) does not support IPv6.
For example our frontend servers no longer use IPv4, as the load balancer handles external traffic, and everything routes internally.
Were just using the ipv6 for internet access (pulling updates).

Proposed Solution

Switch to a registry that supports IPv6, such as:
Docker Hub (native IPv6 support)
Quay.io, Harbor, or cloud registries (AWS, GCP, Azure)

[CommanderStorm]

Note

Ipv6 support for upstream GHCR ipv6 support is tracked here https://github.com/orgs/community/discussions/45930

Docker Hub

We migrated to GHCR as continuing with docker would cost us money in:

• Migrate to GitHub Docker registry #602

We got an email saying that we will need to pay for docker
Context: https://blog.alexellis.io/docker-is-deleting-open-source-images/

Switch to a different registry

Dropping a registry is a major breaking change and we won't be doing this.

Adding another registry though is something that is possible.
If you drop us a PR adding another registry we can add it, as long as their pricing is free for us or you are willing to foot the cost long term..

[nyurik]

Agree with @CommanderStorm (thx!). One thing I think we SHOULD do asap is to add ipv6 support to martin - it should be fairly trivial to do so, but this is a separate thing really. I'm all for publishing the same image to multiple places.