No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

I see Docker hit the limit. Is it on Pulumi Cloud or something I could resolve myself?
``````

Also experiencing this. Right now my only thought is to build and deploy an executor image on a private registry and use the custom exectuor image.

Interested if theres any other fix besides this

it doesnt look like the deployments api accepts anything besides the image ref, how do I configure auth?

Hi! Sorry that y'all hit this. The incident should be resolved now - please let me know if it isn't.

The API does accept authentication to a private registry though, I realize now that we haven't updated the API docs! Let me fix that

Still hitting issues <@U01038HJ93R>

```
  ~  docker:index:Image app updating (2s) [diff: ~build,imageName]; error: error reading build output: node:20-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code <https://registry-1.docker.io/v2/library/node/manifests/sha256:426f843809ae05f324883afceebaa2b9cab9cb697097dbb1a2a7a41c5701de72>: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: <https://www.docker.com/increase-rate-limit> 
23
  ~  docker:index:Image app **updating failed** [diff: ~build,imageName]; error: error reading build output: node:20-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code <https://registry-1.docker.io/v2/library/node/manifests/sha256:426f843809ae05f324883afceebaa2b9cab9cb697097dbb1a2a7a41c5701de72>: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: <https://www.docker.com/increase-rate-limit> 
24
     pulumi:pulumi:Stack client-development-gov running error: update failed 
25
     pulumi:pulumi:Stack client-development-gov **failed** 1 error ```

Got it, seems the issue is still present for folks building docker images in their programs. We're investigating what we can do here.

You can set the `DOCKER_REGISTRY_PASS` and `DOCKER_REGISTRY_USER` environment variables in your deployment settings to avoid hitting rate limits. <https://www.pulumi.com/registry/packages/docker/api-docs/provider/#password_nodejs>

FWIW, you shouldn't be hitting this rate limit anymore. We're also looking into working with DockerHub so we aren't affected by these rate limits in the future.