<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">Here is a sample from a failed build
... <br>
<br>
<pre>docker build . --no-cache ...
Sending build context to Docker daemon 37.68MB
Step 1/9 : <a class="moz-txt-link-freetext" href="FROMgolang:1.19">FROMgolang:1.19</a>
toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and <a class="moz-txt-link-freetext" href="upgrading:https://www.docker.com/increase-rate-limit">upgrading:https://www.docker.com/increase-rate-limit</a>
make: *** [builder-build] Error 1
</pre>
<br>
One thing to note, It's pulls from within our build container
that hits the problem. We don't see it when pulling from bare
metal hardware. <br>
<br>
I've tried raising the issue with the docker community here ...
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/moby/moby/issues/46092#issuecomment-1654243988">https://github.com/moby/moby/issues/46092#issuecomment-1654243988</a>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://forums.docker.com/t/inconsistent-behaviour-of-docker-pull-rate-limit/136896/2">https://forums.docker.com/t/inconsistent-behaviour-of-docker-pull-rate-limit/136896/2</a>
<br>
<br>
We seem to be avoiding the rate limit by using docker login.
Formal StarlingX builds are using a couple of service accounts.
Designers were asked establish there own personal accounts with
dockerhub. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Scott</div>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2023-08-16 16:17, Ildiko Vancsa
wrote:<br>
</div>
<blockquote type="cite" cite="mid:2E3BFA94-F03F-4545-AA3A-7ABAF885B923@openinfra.dev">
<pre class="moz-quote-pre" wrap="">CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Scott,
I looked into the DockerHub download issue again, to the capacity that I could. To confirm what was mentioned already, I have not found anything that would explain what the community is experiencing in terms of rate limits:
- The StarlingX project is still listed as ’Sponsored OSS’: <a class="moz-txt-link-freetext" href="https://hub.docker.com/u/starlingx">https://hub.docker.com/u/starlingx</a>
- The DockerHub docs point to a blog post that says “we will suspend data pull rate restrictions, where no egress restrictions will apply to any Docker users pulling images from the approved OSS namespaces”: <a class="moz-txt-link-freetext" href="https://www.docker.com/blog/expanded-support-for-open-source-software-projects/">https://www.docker.com/blog/expanded-support-for-open-source-software-projects/</a>
- I haven’t received any notifications from DockerHub recently about not meeting the criteria to participate in their open source program anymore
Can you please share a screenshot or the error message that you are getting about hitting a pull rate limit? Also, are you getting that on every repo, or just specific ones?
Once having more background information, I will reach out to the DockerHub team to see what the background issue might be.
Thanks and Best Regards,
Ildikó
———
Ildikó Váncsa
Director of Community
Open Infrastructure Foundation
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>