Docker pull limit reached?

Wappler General Need Help
1

Hi all - I just went to publish my project this morning to a new production server and I'm getting a weird error. Anyone else had this issue or know how to resolve it? Docker website says the limit is 100 pulls in 6 hours - no way I've done that.

This is the error:

image
image1542×115 8.04 KB

What I did:

  1. Created a new Digital Ocean server via resource manager
  2. Added an A record to point my subdomain at the droplet
  3. Added a new target with the new server
  4. Tried to deploy Traefik to the new server

Publishing to the new target also gives the same error.

I have no idea where to start trying to fix this. Grateful for any help!

Thanks

1 Like
2

This is weird indeed you should be able to do like at least 100 requests per 6 hours to hit the limit.

Maybe just login with a free account in docker desktop to increase the limits.

3

Thanks George - this seems to have fixed it. Weird thing is I can publish no problem to the staging server (also remote but previously set up). It's only when I publish to a new target. Anyway, logging into Docker desktop fixed it for now

4

I think the previous owner of the VPS exceeded the limit (before you deployed yours)

5

Possibly - though I did try destroying the server and recreating it with same result. It was all very weird. Works now though :slight_smile:

6

Hi, it’s happened to me too 2 weeks ago!
Had to login on free account and it worked.

7

This just happened to us!

Putting this here if not just for a reminder for myself but as a solution for others with the same issues.

  1. Register on Docker Hub.
  2. Verify your email.
  3. Go to the Docker Hub and login.
  4. Open the Account Menu.
  5. Click on Account Settings.
  6. Click on Personal Access Tokens.
  7. Generate a new Access Token.
  8. Open the Terminal.
  9. Paste in the details provided.
  10. You should now be good to go.
  11. Deploy as normal, and now you should not see the message regarding Pull Limits.

:wink:

1 Like
8

On another Project (Digital Ocean Node Docker) the same thing has just occurred once again @George

May be worth explaining this in the documentation or prompt any User working with Docker to register a Docker Hub account prior to proceeding? Is this worth a Feature Request?

UPDATE, my bad, second Deploy was fine. Very strange. Still could be an issue moving forward with Docker...

9

As it seems like Docker is limiting more and more resources to get you on a paid account, maybe we can support more public registries, like GCL (Google Cloud Registry/Artifact Registry)

GCR already mirrors all public docker hub images, so you can simply add it as a mirror.

So try it out and let me know how it goes.

1 Like