I have a similar bug: for a week, I can’t pull any image from our staging environment via docker-compose but after reading this post, I could do a simple docker pull
.
docker pull postgres:14.13
14.13: Pulling from library/postgres
2d429b9e73a6: Already exists
e19d151f086a: Pull complete
8bcada4d21a4: Pull complete
f208fc972da5: Pull complete
3c98c3576ddb: Pull complete
f588171285a1: Pull complete
40693100d656: Pull complete
df8d3deaa47c: Pull complete
d86466467f89: Pull complete
6ee9a2e499ca: Pull complete
5cb7031207a4: Pull complete
8d484f1e7989: Pull complete
cb05aa8d998c: Pull complete
4827700d7c77: Pull complete
Digest: sha256:9fcd27ebadf8d8fb1f257b1799eff6363cb0d947ffff046de5d49915f469ca08
Status: Downloaded newer image for postgres:14.13
docker.io/library/postgres:14.13
but:
docker compose pull
[+] Pulling 15/15
✔ mqttlistener Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker_stream Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker_abnormal_consumption Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker_command Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ api Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker_aggregation Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ worker_mqtt Skipped - Image is already being pulled by worker_mqtt_telemetry 0.0s
✔ postgres Pulled 0.8s
✔ worker_mqtt_telemetry Pulled 0.6s
✔ warp10 Pulled 0.5s
✔ mqtt Pulled 0.9s
✘ redis Error toom... 1.1s
✔ webapp Pulled 0.6s
✔ backup Pulled 0.5s
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
Above, redis
, postgres
and emqx
are hosted on docker hub. redis
and postgres
are official images whereas emqx
which is pulled is from a user repo emqx/emqx
and not the official image. All other images are pulled from our internal gitlab registry.
We are not authenticated on docker hub as we don’t have any subscriptions yet.
docker compose pull mqtt
[+] Pulling 1/1
✔ mqtt Pulled
but:
docker compose pull redis
[+] Pulling 1/1
✘ redis Error toomanyrequests: You have reached your pull rate limit. You may increase the limit by... 1.1s
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
As I just pulled postgres via docker pull
it now works again:
docker compose pull postgres
[+] Pulling 1/1
✔ postgres Pulled
but before that it failed.
dpkg -l docker*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=========================-=============================-============-================================================>
un docker <none> <none> (no description available)
ii docker-buildx-plugin 0.17.1-1~debian.11~bullseye amd64 Docker Buildx cli plugin.
ii docker-ce 5:27.3.1-1~debian.11~bullseye amd64 Docker: the open-source application container en>
ii docker-ce-cli 5:27.3.1-1~debian.11~bullseye amd64 Docker CLI: the open-source application containe>
ii docker-ce-rootless-extras 5:27.3.1-1~debian.11~bullseye amd64 Rootless support for Docker.
ii docker-compose-plugin 2.29.7-1~debian.11~bullseye amd64 Docker Compose (V2) plugin for the Docker CLI.
un docker-engine <none> <none> (no description available)
un docker.io <none> <none> (no description available)
lines
And containerd.io 1.7.23-1
From our CI server we have no troubles at all whereas it pulls more image than our staging environment.
So are there some special restrictions on official images that are less or not present on user based images ?