News for hackers. Stuff that matters.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by zspitzer on Friday February 21, 2025 @05:11AM (#43125898)
This ain't great for Github Actions, as PRs might now fail as there are no secrets available, randomly depending on your runner's IP

Also it still takes some gymnastics to optionally support docker creds in a workflow https://github.com/orgs/community/discussions/131321

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by 05 on Friday February 21, 2025 @05:28AM (#43125991)
Just mirror what you need to ghcr, I guess..
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by MrBuddyCasino on Friday February 21, 2025 @05:16AM (#43125933)
OTOH, I don't understand by the big cloud platforms don't support caching, or at least make it easy. Azure pulling container dependencies on every build just feels rude.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by InsomniacL on Friday February 21, 2025 @06:47AM (#43126457)
Is there any licence constraints?

I.e Docker terms of service restrict distribution in this way?

Is there any technical restraints?

I.e Docker specify no-cache

I expect Docker don't want their images cached and would want you to use their service and transform you in to a paying subscriber through limitations on free tier.

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by aragilar on Friday February 21, 2025 @08:17AM (#43127073)
Caching is called out on https://docs.docker.com/docker-hub/usage/manage/.

My feeling is the way the naming scheme was defined (and subsequent issues around modifying the default registry), docker wanted to try to lock people into using docker hub over allowing public mirrors to be set up easily. This failed, so they've needed to pivot somewhat to reduce their load.

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by InsomniacL on Thursday February 27, 2025 @11:00AM (#43195594)
> This failed, so they've needed to pivot somewhat to reduce their load.

Or it worked, and now through free tier limitations they get more people sign-up and more people taking paid subs

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by wkat4242 on Friday February 21, 2025 @05:57AM (#43126197)
Yes rude and lazy on their part.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by martypitt on Friday February 21, 2025 @05:25AM (#43125975)
Gitlab does this, and it works nicely
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by terminalbraid on Friday February 21, 2025 @01:16PM (#43130938)
Seconding, though it does require some setup at least for self-hosted. Gitlab also has a full container registry built in, so it's not difficult to pull the image you want, push it to gitlab, and reference that going forward.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by hahn-kev on Friday February 21, 2025 @05:35AM (#43126041)
Yeah I don't get why I have to setup caching myself for this kind of thing. Like wouldn't it be more efficient to do it lower down in their infra anyway?
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by mmbleh on Friday February 21, 2025 @10:21AM (#43128458)
These platforms do cache quite a bit. It's just that there is a very high volume of traffic and a lot of it does update pretty frequently (or has to check for updates)
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by MrBuddyCasino on Friday February 21, 2025 @02:29PM (#43131842)
Are you saying they cache transparently? Because I haven't seen that mentioned in the docs.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by everfrustrated on Friday February 21, 2025 @09:17AM (#43127689)
Unless something has changed, GitHub pays a license to Docker to allow their runners IP space to avoid the rate limit.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by immibis on Friday February 21, 2025 @12:16PM (#43130154)
Which means GitHub is going subscription-only in the near or mid-term future. Will we repeat the same mistakes?
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by blitzar on Saturday February 22, 2025 @04:09AM (#43137436)
Rate limit the number of lines of code changed or pulled per day for free accounts.
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by baby_souffle on Friday February 21, 2025 @10:40AM (#43128740)
TIL! Can you link to a source for this? I am curious!
Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by everfrustrated on Friday February 21, 2025 @11:13AM (#43129216)
May not be true anymore but was in the past when Docker first introduced the limits.

Very hard to find anything definitive still left on the web. This is all I could find...

https://github.com/actions/runner-images/issues/1445#issueco...

https://github.com/actions/runner-images/issues/1445#issueco...

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by baby_souffle on Friday February 21, 2025 @11:06PM (#43136007)
Thanks!

> Very hard to find anything definitive still left on the web

Probably a lot happened behind closed doors so there probably wasn’t much to begin with.

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by kylegalbraith on Friday February 21, 2025 @11:44AM (#43129690)
As someone mentioned, GitHub has something to prevent this, but it's unclear (or at least undocumented) what.

We at Depot [0] work around this by guaranteeing that a new runner brought online has a unique public IP address. Thus avoiding the need to login to Docker to pull anything.

Subsequently, we also do the same unique public IP address for our Docker image build product as well. Which helps with doing image builds where you're pulling from base images, etc.

[0] https://depot.dev

Re:Docker limits unauthenticated pulls to 10/HR/IP from Dock... by Lammy on Saturday February 22, 2025 @01:16AM (#43136540)
I'm curious about this regarding GCP as well. I have a few Cloud Run Containers set up pulling their image directly from Docker Hub, then injecting my single config file from a Secrets-Manager-backed volume mount. That way I don't have to maintain my own package in GCP's Package Registry when the upstream project only publishes to Docker Hub