When running a ./launcher rebuild app, I get the following errors: x86_64 arch detected. WARNING: We are about to start downloading the Discourse base image This process may take anywhere between a few minutes to an hour, depending on your network speed Please be patient Error response from da…

Where are you hosted? I’ve opened a support case with DigitalOcean for this and have a confirmation that this is an issue, but for ipv6 enabled droplets only. Docker Hub is rate limiting based on the net range instead of a single IP for ipv6 (which depletes 100 pulls per 6 hours for anonymous pull…

I tried again 10 hours later. Same result. The docker hub time window is 6 hours. This is a clean discourse install within the last 40 days. No plugins or customization at this time. So…. How is discourse hub accessed from a credential perspective? Anonymous? Discourse login? Is there a way to se…

A possibly useful test is the very small hello world image: /var/discourse# docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 478afc919002: Pull complete Digest: sha256:5b3cc85e16e3058003c13b7821318369dad01dac3dbb877aac3c28182255c724 …

Same results: docker run hello-world Unable to find image ‘hello-world:latest’ locally docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: Docker Hub usage and limits | Docker Docs . See ‘docker r…

I just encountered this problem on two Discourse forums (different servers/IPs). Please be patient 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 Error respon…

This is what Docker’s AI assistant says, but the new rate limits aren’t supposed to happen until March 1st. (If Discourse makes more than 10 pulls during a rebuild, that’s probably going to affect people. Edit: it looks like it’s already limited to 10 .) Based on the knowledge sources provided, it …

Thank you for validating the problem is not just my system. I was able to upgrade both the docker manager and discourse system levels from within admin without any issues. Any time I try to run a launcher rebuild, I get the rate limit errors.

Updating appears to be working from the dashboard on both the forums that are rate-limited in the terminal.

My sites are on DigitalOcean with IPv6 enabled.

Same issue then, try disabling ipv6 on the DO web mgmt if you don’t need it for some other service (I think you can do it without rebooting the droplet) and try again.

I don’t see a way to turn of IPv6 in the droplet settings, but I’ll take a closer look later. I was wrong about the updates working from the dashboard. One worked but the other one crashed in the middle. The dashboard now says that it’s out of date: Edit: the message went away after rebooting the…

Docker 레이트 리밋 오류: 런처 재빌드 시 발생

지원

LotusJeff 12월 24, 2024, 9:47오후 13

Turning off IPv6 on the Digital Ocean server solved the issue: Here is instruction from DO on how to turn off IPv6.

Getting 502 Bad Gateway after attempting upgrade

글		댓글	조회수
Discourse Update Error: Your Docker installation is not working correctly Support	7	324	2월 8, 2025
Unable to start discourse due to rubygems rate limiting Support	43	3656	6월 14, 2018
Getting 502 Bad Gateway after attempting upgrade Self-hosting	2	186	12월 30, 2024
Can't get discourse working again Self-hosting	8	1858	2월 16, 2020
Which rate limit applies to the `/u/by-external/{provider}/{external_id}.json` endpoint? Development rest-api	2	91	7월 9, 2024

Docker 레이트 리밋 오류: 런처 재빌드 시 발생

Related topics