AIO update fails because of Docker Hub rate limits

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , ,
1

AIO update fails because of Docker Hub rate limits. I get error messages like this:
Message: Could not pull image nextcloud/aio-whiteboard:latest: {"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}

Logging in to Docker in CLI didn’t change anything, the same error message remains. I can still pull images in CLI, it seems the problem only happens inside the container.

Quickfix: pull all the images manually in CLI with sudo docker pull nextcloud/aio-mastercontainer, sudo docker pull nextcloud/aio-apache, etc.

Better solution:
It would be nice to have an alternative repository for all the docker images, that doesn’t have the rate limits of the Docker Hub, like there is for the simple non-AIO Nextcloud here: nextcloud - LinuxServer.io Edit: there is one at Package all-in-one · GitHub (at the moment only in beta)

2

Why are 10 pulls per hour too few for Nextcloud?
Then you need to use a corresponding Docker Hub account.

3

Hello @jch, indeed starting april 1st, docker hub decreases the anonymous pulls from 600 per hour to 10 which breaks AIO. Fortunately we just moved almost all images to ghcr.io which does not have such limits and released it with AIO v10.10.0 Beta. You can switch to it by using the ghcr.io/nextcloud-releases/all-in-one:beta tag instead of nextcloud/all-in-one:latest for now. Please let me know if that fixes the problem for you!

1 Like
4

Nice, I solved it for now by pulling every image one by one but this will be better long-term. I’m not sure why I hit the rate limit already since it’s supposed to start on April 1st…

5

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.