You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice to see the addition of a parameter that sits above any commands that do docker pull operations. This parameter would just be a number to stipulate how many times the script should retry docker pull failures before aborting the pipeline
Something like: docker-pull-retries: 3
Why is this needed
The majority of our pipeline failures occur around a TLS timeout when doing pull operations (in our case doing the build-and-push-image command). The impact of this failure can be reduced by implementing a pause and retry pattern.
example of error:
Successfully created context "builder"
Unable to find image 'tonistiigi/binfmt:latest' locally
latest: Pulling from tonistiigi/binfmt
64c318a5: Pulling fs layer
docker: error pulling image configuration: ... : net/http: TLS handshake timeout.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue. While it could be done, it does add some verbosity to the parameters. We’ll wait for a while to look for any community feedback before moving forward. I've added this to our backlog for now.
Similar to #215, we experience regular enough failures due to connectivity issues that having a built in ability to retry would be of tremendous value.
What would you like to be added
Would be nice to see the addition of a parameter that sits above any commands that do docker pull operations. This parameter would just be a number to stipulate how many times the script should retry
docker pull
failures before aborting the pipelineSomething like:
docker-pull-retries: 3
Why is this needed
The majority of our pipeline failures occur around a TLS timeout when doing pull operations (in our case doing the
build-and-push-image
command). The impact of this failure can be reduced by implementing a pause and retry pattern.example of error:
The text was updated successfully, but these errors were encountered: