https://pulumi.com
Join Slack
This message was deleted.
s

Slackbot

about 4 years ago
This message was deleted.
s
j
f
  • 3
  • 3
  • 144
This message was deleted.
s

Slackbot

about 4 years ago
This message was deleted.
s
j
p
  • 3
  • 5
  • 143
Hey guys, I get the `error: booting builder: context deadline exceeded` when trying to build an imag...
m

M.M

6 months ago
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.
m
e
  • 2
  • 2
  • 142
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
j
n
  • 3
  • 2
  • 142
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
j
r
  • 3
  • 7
  • 142
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
p
+2
  • 4
  • 7
  • 142
This message was deleted.
s

Slackbot

over 4 years ago
This message was deleted.
s
m
j
  • 3
  • 8
  • 142
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
j
l
  • 3
  • 2
  • 141
good afternoon! i've got a weird issue that i hope might pique somebody's curiosity. i have a projec...
f

Fotios Lindiakos

8 months ago
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?
f
  • 1
  • 2
  • 140
This message was deleted.
s

Slackbot

over 3 years ago
This message was deleted.
s
s
j
  • 3
  • 11
  • 140
Previous293031Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by