This message was deleted.

This message was deleted.

Hey guys, I get the

error: booting builder: context deadline exceeded

when trying to build an image using docker-build provider. I use following code when trying to build the image:

image, errCreatingImage := dockerbuild.NewImage(context, name, &dockerbuild.ImageArgs{
		Push: pulumi.Bool(true),
		Tags: pulumi.StringArray{
			pulumi.String(imageId),
		},
		Dockerfile: &dockerbuild.DockerfileArgs{
			Location: dockerfileLocation,
		},
		Context: &dockerbuild.BuildContextArgs{
			Location: location,
		},
	}, pulumi.Timeouts(&pulumi.CustomTimeouts{Create: "30m"}), pulumi.DependsOn(dependsOn))

I've verified that docker build context location is correct and Dockerfile location is also correct by building the image from terminal. For the sake of simplicity and debugging I've replaced my Dockerfile original contents with following: "FROM hello-world", but error is still there. Would be grateful if anyone could point me in the right direction.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

good afternoon! i've got a weird issue that i hope might pique somebody's curiosity. i have a project (all AWS provider and configured to use OIDC) that's working just fine in

us-east-1

. i added a second stack to use

aws:region: eu-central-2

and then the preview fails with

Diagnostics:
  pulumi:pulumi:Stack (networking-xxx-stg.eu-central-2):
    error: awsx:ec2:Vpc resource 'xxx' has a problem: grpc: the client connection is closing
 
  pulumi:providers:aws (default_6_47_0):
    error: pulumi:providers:aws resource 'default_6_47_0' has a problem: Invalid credentials configured.

so here's the fun part. i set

AWS_REGION=eu-central-2

for that stack and it worked. looking into the cloudtrail logs, it looks the one that failed was issued an access key from

us-east-1

. the one that succeeded was issued from

eu-central-2

. this leads me to believe that the ENV var is influencing whatever you run initially to do the

AssumeRoleWithWebIdentity

(from the deployment logs, it looks like its calling

pulumi-deploy-executor oidc ...

) considering this isn't documented anywhere when talking about configuring the regions, i'm assuming this is not expected?

This message was deleted.