We’re using Harbor as our container registry, and we want to enable automatic image vulnerability scanning on push.
When doing a
put using the
image resource, Concourse successfully pushes the image, but then immediately tries to pull the image again. Because Harbor (Trivy, in our case) is still scanning the image, the pull fails, and consequently the entire task fails.
I’ve tried using
attempts to force a retry, but this re-tries the entire build-and-push process, which just perpetuates the problem.
Is there a way I can avoid the image resource attempting a
pull after a
push, or somehow introduce a delay/retry into this process?