[Starlingx-discuss] How to avoid DockerHub download rate limit when building StarlingX

[Ildiko Vancsa]

Hi,

Thanks Davlet for sharing a workaround.

I also asked about alternatives in the #opendev channel. The team hasn’t done an extensive research before deciding with Quay.io. They were considering that service or hosting a registry themselves. The Zuul community already migrated over to Quay, while OpenDev still has some dependencies on Docker that causes delays. I was also pointed at the Sovereign Cloud Stack community, who hosts their own registry, based on Harbor, which is an open source tool: https://sovereigncloudstack.github.io/website/tech/2023/05/30/registry-migration-upgrade/

You can find the entire conversation here: https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-07-26.log.html#t2023-07-26T15:45:40


In summary, the following alternatives came up so far:

- Quay - https://quay.io
- Harbor - https://goharbor.io
- Nexus Repository - https://www.sonatype.com/products/sonatype-nexus-repository


I hope this helps.

Best Regards,
Ildikó


> On Jul 26, 2023, at 17:03, Panech, Davlet <Davlet.Panech at windriver.com> wrote:
> 
> Good day,
> 
> As DockerHub has recently changed its download rate restrictions policy, you may have experienced errors while building StarlingX, similar to:
> 
> "You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"
> 
> While the build team is pondering a permanent solution, there are a few steps you can take that *may* alleviate this problem, depending on the network configuration of your build environment:
> 	• Register an account with Docker Hub
> 	• Use the "--dockerhub-login" command-line option when calling "stx-init-env" to start the build environment (new option that merged recently)
> 	• Use "docker login" inside the build container before building app containers
> Hope this helps,
> D.
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io