Getting "No digest available for image" when building Docker image #200
Comments
|
That error shows up because the execution of |
|
Thanks, @leezen , I will check this out. |
|
I'm running into this too - it's intermittent. Disabling building of local images doesn't appear to affect this. |
|
We tried to see if this was a concurrency error with building multiple images in parallel - but it's not. Still occurs even if the images are forced to be built sequentially. It looks like a race condition with the digest not being available immediately after the image is built - why is the digest needed in the first place? |
|
So I figured this out based on our debug logs (which I have anonymized somewhat here) The problem is that as we're building multiple images in parallel, Pulumi attempts to compute the digest for one image before it finishes being built:
This is not the case for Are there any work-arounds for this in lieu of a fix? |
|
cc @leezen on the above |
|
@Aaronontheweb Thanks for the extensive debugging output. We'll have to take a deeper look at this. At a cursory glance, I wouldn't expect the |
|
could it be an issue with building multiple images in parallel? |
|
Hello, We are also experiencing this issue. We are trying to build 3 docker images for use in AWS Fargate. We are running pulumi 2.10.1, pulumi docker 2.2.3, pulumi aws 2.11.0, pulumi 2.5.0. Language C#. Frequency: Once we start getting the error, it happens every single execution for a bit after. Different Images however, produce the error |
|
I noticed |
|
It took a while to reproduce this issue locally, but I got it now. However, based on the logs, the I'm deploying 30 images at the same time, so there is a bunch of chatter in between where The sequence of log statements makes sense and yet the error happens. I'll keep digging. |
|
Thanks for looking into this @mikhailshilkov - really appreciate it |
|
It turns out that we are missing stdout content due to a race condition, which leads to Reviews are welcome! |
That's a good point, but probably not related to this particular issue. I think I'll fix that in the same PR while I'm making a change. |
|
@mikhailshilkov Thanks! Is it going to be released anytime soon? |
|
You could give it a try right now if you are okay with using an alpha version for a little while: https://www.nuget.org/packages/Pulumi.Docker/2.4.0-alpha.1601877083 |
|
@mikhailshilkov Been using it for majority of the day today and works as expected. Thanks for the quick turn-around look forward to the next prod release to update the dependancies. |
|
We're using it as well and I believe the issue has been resolved for us |
|
Hi all I have just made v2.3.1 release that includes this bug fix Paul |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello guys.
From time to time, we are getting the following error during CI build:
Before that, we have image built successfully, but having there this error too:
What does this exception mean, and how can we fix it?
Thanks!
The text was updated successfully, but these errors were encountered: