Hello, we are currently experiencing some problems with our build process. This is what we found in logs:

2020-11-16T17:02:04.277+01:00	#9 [stage-0 1/9] FROM <http://docker.io/spryker/php:7.3|docker.io/spryker/php:7.3>
2020-11-16T17:02:04.277+01:00	#9 digest: sha256:b85b8505f81ab86b2c64ea0e4f7c5c9138a7b5083a05311ac5348b8e82e03844
2020-11-16T17:02:04.277+01:00	#9 name: "[stage-0 1/9] FROM <http://docker.io/spryker/php:7.3|docker.io/spryker/php:7.3>"
2020-11-16T17:02:04.277+01:00	#9 started: 2020-11-16 16:02:00.477880875 +0000 UTC
2020-11-16T17:02:04.277+01:00	#9 completed: 2020-11-16 16:02:01.582288222 +0000 UTC
2020-11-16T17:02:04.277+01:00	#9 duration: 1.104407347s
2020-11-16T17:02:04.277+01:00	#9 error: "failed to copy: httpReaderSeeker: failed open: unexpected status code <https://registry-1.docker.io/v2/spryker/php/manifests/sha256:854e5698492a269292dcdbc82ba08d878e4e9943adb10f0d37288ff0c5762c09>: 429 Too Many Requests"

I will try to trigger the build process again later but wanted to ask already here. Did anyone experience this issue?

I've heard that docker hub has limits for pulling now. Is this a case maybe @high-pencil-62400?

Looks to me like we will have to take the spryker docker images and upload them to some other image repository so they can be pulled from there? Or do you already have some other solution for this?

xxx [7:22 PM]
FYI we're experiencing issues with pulling docker images in cloud, possibly someone else is affected. It's caused by recently introduced limits in docker hub: <https://www.docker.com/blog/what-you-need-to-know-about-upcoming-docker-hub-rate-limiting/>

yyy  [8:03 PM]
We are addressing it in the cloud already, locally you should use an account

¯\_(ツ)_/¯

well we are using cloud (sort of) as well

But from what I've seen in DevOps community's slack, some solve this using Nexus proxying and using --registry-mirror on clients.

How is it solved in spryker cloud?

Probably it's not yet solved.