Allow custom "Build Error" Docker image
K
Kelvin Tay
Right now, when an invalid config is pushed, the "Build Error" job is seen.
Here is an example on CircleCI Cloud: https://app.circleci.com/pipelines/github/kelvintaywl-cci/debug-curl-403/2/workflows/9268fa1b-5c48-4647-88d0-4c227b6cfded/jobs/4?invite=true#step-0-13
We can see that it will pull a
bash:4.4.19
Docker image by default.It would be great to be able to customize this default Docker image (i.e., choose a different image), for Server.
Alternatively, can the "Build Error" job be implemented such that it doesn't require pulling an image?
For Server customers with restricted Docker registry setup, it may be beneficial for them to be able to specify an approved image.
B
Billy Keyes
This is also important for Server customers who use an internal Docker registry to avoid rate limits from Docker Hub. We recently had a "Build Error" job fail because Circle hit rate limit attempting to pull the
bash
container:Starting container bash:4.4.19
Warning: No authentication provided, using CircleCI credentials for pulls from Docker Hub.
image cache not found on this host, downloading bash:4.4.19
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