CI job used wrong image apparently deliberately
In https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/jobs/578718 I saw this:
Using Docker executor with image rustlang/rust@sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e ...
Pulling docker image rustlang/rust@sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e ...
WARNING: Failed to pull image with policy "always": initializing source docker://rustlang/rust@sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e: reading manifest sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e in docker.io/rustlang/rust: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit (manager.go:250:126s)
Attempt #2: Trying "if-not-present" pull policy
Using locally found image version due to "if-not-present" pull policy
Using docker image sha256:1da0665db7260e841644b11b73163035f642ff5b7ca9ec57f1ee5d8cd9608b16 for rustlang/rust@sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e with digest docker.io/rustlang/rust@sha256:aaee57e8fa29c2809494ec71ffab6fcfa241b765c2a78d781e4de17fe38f060e ...
IHNI where it got the image it decided to use instead, but this is definitely Not Ok.
There's #41621 too, but I think Jim would have noticed messages like the ones above.