Docker pull limit reached, but only for n8n images

Questions
1

I’m running into a strange issue. I cannot pull the latest n8n image from docker hub.

I get this error if I try: docker pull docker.n8n.io/n8nio/n8n:1.67.1

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: Understanding Your Docker Hub Rate Limit | Docker

Thing is : I am not pulling more than 100 images every 6 hours. I’m not even pulling almost anything.

What’s also strange is that if can pull anything else without any problem (Wordpress, MySQL etc. etc.) …

How can this be only throwing the rate limit error for n8n? What am I missing here ?

1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Can you please try docker pull n8nio/n8n:1.67.1 to pull from docker hub directly?

1 Like
4

Tried that as well … same result …

5

Update: I waited over 6 hours (dockerhub rate limit is 100 pulls per 6 hours). Now I was able to get the image with the direct pull. However, if I try pulling through docker compose, it still tells me that I have hit the pull rate limit (which is nonsense, because I’ve not been pulling or doing anything).

Honestly, it’s a mystery to me at the moment. I have n8n running behind nginx proxy manager, and nothing else is happening. What’s even stranger is that this issue suddenly appeared, out of the blue …

6

Hmm it wasn’t clear if you tried with an authenticated account but anonymous accounts to dockerhub are limited per IP address.

“Per IP address” may mean everyone in the same office building or coffee shop or data center - ie using the same network or pool of addresses.

Definitely recommend using an authenticated account.

7

I tried it anonymously, but also with authenticated pull (as that increases the pull limit to 200, instead of 100). I’m self-hosting n8n on a digitalocean VPS.

The only thing I can think of now still, is that it’s a DO thing that’s going on.

I might snapshot the whole thing and try it on a different VPS. with another IP , to see if that’s the problem …

I also learned that docker compose treats pulls differently than a direct pull … though still, really it doesn’t make any sense …

8

I had the exact same issue. May I know the exact steps you took to solve the problem? I am a noob and dont really understand what you meant by direct pull.

9

A direct pull is : `pull n8nio/n8n:1.67.1’ , which does not pull through a command in a docker compose file.

The direct pull seems to work, while pulling from a docker compose file does not …

10

normal we would

  1. docker compose pull
  2. docker compose down
  3. docker compose up -d

if i do docker pull n8nio/n8n:1.67.1

what should my next commands be?

11

After changing the image line to the correct n8n version number inside your docker compose file (.yml file), you can normally run docker compose up—d.

You can check if the correct image is pulled with ‘docker image ls’.

12

Update: I’ve switched IP addresses by generating a snapshot of the server and creating another VPS droplet with another IP.

The same issue while pulling through docker compose … So no difference.

Anyone else running into this problem?

13

yea i have the same problem + many active workflows have stopped working automatically after the last update I did 1.68.0. Quite frustrating when things that were working before normally don’t after an update.

14

For anyone running into this problem, you might still be able to pull the n8n image with a direct docker pull, e.g. : docker pull n8nio/n8n:1.69.2

I’ve also started a thread on the Docker forums, and some people face the same issue - Docker forum thread

For now, I don’t know the solution, but I guess that it’s on the docker engine side of the coin …

We’ll see what happens with time …

15

Update:

So, for some odd reason, docker compose pulls for n8n are back working normally for me.

In the mean time, I’ve posted on the docker forums, and in some other places - and there were many people experiencing compose pull issues (for various images).

My conclusion is that it was a docker hub bug, though I’m not sure.

Anyone else who experienced this issue, notice that it’s working again ?

16

Just freshly updated to 1.70.3 on my Digital Ocean droplet.

Direct pull still worked:

docker pull n8nio/n8n:1.70.3

…But the typical pulls did not:

docker compose pull
 ! n8n Warning  toomanyrequests: You have reached your pull r... 

docker pull docker.n8n.io/n8nio/n8n
Using default tag: latest
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit