Docker rate limit warning appears inaccurate
Answered
TeamCity Professional 2020.2.3 (build 86002)
We are getting Docker rate limit warnings on builds that don't use Docker at all. They are a part of a parent project that has some build configurations which use a root project build template to do docker operations. But the builds not pulling from Docker I would not expect to see the warning. What's the logic?
[17:08:57]Docker rate limit warning
[17:08:57][Docker rate limit warning] This build pulls images from Docker Hub without authentication, which might cause reaching the download rate limit. Consider configuring an authorized connection to Docker Hub or pulling from a Docker Hub mirror instead. Read more: https://docs.docker.com/docker-hub/download-rate-limit/
[17:08:57][Docker rate limit warning] Related images:
[17:08:57][Docker rate limit warning] - pulumi/pulumi:latest
[17:08:57][Docker rate limit warning] - library/busybox:latest
Please sign in to leave a comment.
Also for a valid use of that warning, the warning doesn't seem to disappear after adding authentication and re-running the build. The warning goes away in the build log but remains at project level. Is it cached for a certain period?
Same issue here, both in 2020.2.2 and 2020.2.3. Also, a slightly different issue may occur: the build indeed pulls from DockerHub, but it pulls a different image than the one shown in "Related images".
Also seems to be related to https://youtrack.jetbrains.com/issue/TW-70882.
Hello Geoff, Petr,
Yes indeed, this appears to be a case of TW-70882; I have added an internal reference on this thread to the issue. Please feel free to comment or vote on it as you see fit; as soon as the issue status is updated it will be reflected on the tracker. Petr, speaking of the other problem with Related images not matching the actual images pulled, could I ask you to share the details (build log and a screenshot of related images list) via https://uploads.jetbrains.com, so I would check with the development team if this is another symptom or a separate issue?
Actually I don't seem to be able to find the build any more. Chances are that I was wrong. Nevertheless attached is the occurrence of a build that doesn't pull anything yet the warning is shown.
Upload id: 2021_04_07_RAn7T1SCcKaPaj3t
Hello Petr,
Thank you! The developer who is working on the TW-70882 confirmed it is the same issue; the fix for the incorrect Related images is already done, so we should expect the issue to be fixed in 2020.2.4 release.