Sponsors needed: Docker image mirror [SOLVED]

[michael]

On November 1, 2020, Docker will commence to enact limits on free repositories. The two limits in question are:

1- Inactive image retention for up to 6 months.
2- A maximum of 100 image pulls in a six-hour window.

Edit: The first concern is that it is not clear what "inactive" images refer to. (This is now clear).

The second and more serious concern is that our Docker image due to the popularity of the project, far exceeds the pull rate.

Using Docker Hub's API we measured the download rate with the following command line. It outputs the timestamp and the current image pull count.

Code: Select all

date +%s; curl https://hub.docker.com/v2/repositories/mayanedms/mayanedms/ -s -o -| jq .pull_count | xargs printf "%'d\n"

This gave us the following numbers:

1598297810
5,295,982

1598298459
5,296,085

2020-08-24_16-20.png (22.82 KiB) Viewed 866 times

Or 103 pulls in 10.8 minutes. Our image will reach the pull limit in roughly 10 minutes. In other words, our image will only be available for download for a 10 minute window every 6 hours, or 40 minutes per day.

This will severely affect the access to the project.

We already have self hosted backup repositories for emergencies, but these have a 1TB outbound bandwidth limit per month. If we use these backup repositories, the bandwidth limit would be reached in 1 hour, making the mirror unusable for the rest of the month.

The solution is to have multiple mirrors hosting the image.

If you are able to provide a mirror please comment below or reach out via email to info@mayan-edms.com

These limits will go into effect on November 1, that gives us 36 days to build it a mirror network before users start experiencing downloading Mayan EDMS.

Thank you for your support.

[drilling005]

I don't believe this should impact the project - the Docker download rate limit docs (https://docs.docker.com/docker-hub/download-rate-limit/) say:

Limits are applied based on the user doing the pull, and not based on the image being pulled or its owner.

This just applies to the individual performing the "docker pull" command and whether or not they've previously authenticated with the repository using "docker login".

[michael]

That makes total sense! Thanks a lot for the clarification.