Docker Apps frequently refusing to run because of pull rate limit

TrueNAS General
1

I frequently have docker apps refusing to run because of pull rate limit. I am nowhere near the actual limit, but it probably lumps me with other people from my ISP.

Regardless though, this is utterly ridiculous. If a pull fails it should just run the current version I have installed.

Also why is it spamming the server with pulls? It should at least be checking how long it has been since the last pull attempt and only do a pull on start if it has been at least X hours (exact value up for debate).

if the pulls are unavoidable, then it should have a build in mirror and set itself as the mirror. pull from localhost on launch. and have the built in mirror update online once a day.

The fact I can’t literally launch an app I already have installed because I need to first ask permission from some nebulous online entity is ridiculous.

2

If you’re behind CGNAT (as is probably the case) then use Apps → Configuration → Sign in to a Docker registry to avoid getting lumped in with others on the same “public IP”

3

You can use mirror.gcr.io.

CleanShot 2026-02-06 at 01.23.16@2x
CleanShot 2026-02-06 at 01.23.16@2x2018×818 324 KB

4

Thank you for the workaround suggestions. They are very useful.

Regardless of workarounds, this is still a bug that needs to be fixed.

Apps should just run with existing version if pull request is denied by server.

Also mirror.gcr.io should actually be https://mirror.gcr.io/ . as trying to just input it without the https:// results in an error. Warning: The moment you hit save setting it will instantly kill the docker app and with it all currently running apps.

5

I suspect this isn’t classified as a bug, it’s just not implemented very well.

If you want a chance for real change you could try a Feature Request in the forum.