Docker sponsorship and/or alternate container registry options

[surrealchemist]

I manage a few applications using deno, and they are hosted in AWS ECS. The problem I am seeing is that because it has to pull from docker's registry directly using AWS pipelines that are on shared infrastructure, I am easily hitting rate limits causing builds to fail.

I would propose one or more of these if possible:
Go through the process to apply for Docker-Sponsored open source program. This will remove rate limits for all users.
Add publishing to alternate registries to give users options. Having it available via AWS ECR Public Gallery, and/or another public registry like quay.io

[surrealchemist]

I saw the sponsorship showed up on the docker hub page. I thought it may have fixed our problem but I think it might still occur if you aren't authenticated. Having it up on the ECR public gallery would be a benefit for hosting things in AWS as it would pull from within their network and not be rate limited.