Are Pulumi builders unavailable? Possible impact f...
# general
l
Are Pulumi builders unavailable? Possible impact from AWS' trouble this morning? We've been getting this error message for the last hour. Pulumi status doesn't show any issues and support hasn't gotten back to us yet.
Copy code
listing workers for Build: failed to list workers: unable to acquire builder: unavailable: Unable to acquire machine, please retry
s
This is for Deployments?
l
Yep
s
I believe we are affected by the AWS outage. I'll work to get the status page updated. Apologies for that.
👍 1
Status page should be updated shortly if not already. Thank you so much for bringing this to our attention. We'll of course be looking at why we didn't catch this before you did.
l
Thanks, saw the update go out
s
When you say "Builders", where are you seeing this issue? What service or SaaS? Is this in the Pulumi Cloud console?
l
Yep in the Cloud console under "Updates" for our stacks
👍 1
q
Hey @lively-kilobyte-71239, are you getting this error when trying to build container images? Are you integrating with remote docker builders for that?
l
Let me check
Ah, yep looks like we are using Depot.dev for building the docker containers. Appears they're reporting issues as well
q
Got it! Yes, I think in this case it's not Pulumi Deployments that's having issues. The deployment seems to start - building the image fails because Depot is having issues. You could try temporarily falling back to building without the remote builder
l
Thanks, we'll try that