# AIO update fails because of Docker Hub rate limits **URL:** \ **Category:** 📦 Appliances (Docker, Snappy, VM, NCP, AIO)\ **Tags:** update\_problems, docker, linuxserverio, aio\ **Created:** [March 25, 2025, 10:41am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033 "2025-03-25T10:41:57Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jch](https://help.nextcloud.com/letter_avatar/jch/32/6_22734026db12803ebb3e059622ac3534.png) [@jch](https://help.nextcloud.com/u/jch)\ **Post date:** [March 25, 2025, 10:41am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033/1 "2025-03-25T10:41:57Z")
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](https://docs.linuxserver.io/images/docker-nextcloud/) **Edit** : there is one at [Package all-in-one · GitHub](http://ghcr.io/nextcloud-releases/all-in-one:beta) (at the moment only in beta) ---
**Author:** ![amateurkicker](https://help.nextcloud.com/letter_avatar/amateurkicker/32/6_22734026db12803ebb3e059622ac3534.png) [@amateurkicker](https://help.nextcloud.com/u/amateurkicker)\ **Post date:** [March 25, 2025, 10:46am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033/2 "2025-03-25T10:46:01Z")
Why are 10 pulls per hour too few for Nextcloud? Then you need to use a corresponding Docker Hub account. ---
**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\ **Post date:** [March 25, 2025, 10:48am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033/3 "2025-03-25T10:48:21Z")
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](http://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! ---
**Author:** ![jch](https://help.nextcloud.com/letter_avatar/jch/32/6_22734026db12803ebb3e059622ac3534.png) [@jch](https://help.nextcloud.com/u/jch)\ **Post date:** [March 25, 2025, 11:00am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033/4 "2025-03-25T11:00:13Z")
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… ---
**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\ **Post date:** [April 2, 2025, 11:00am UTC](https://help.nextcloud.com/t/aio-update-fails-because-of-docker-hub-rate-limits/221033/5 "2025-04-02T11:00:23Z")
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.