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.

Pulumi Community

it shouldn't take 40 minutes :disappointed: how do you auth to AWS?

In the credentials file (.aws/credentials). Where there is only the [default] entry with aws_access_key_id and aws_secret_access_key

you might want to `ctrl + c` it I'm afraid

Okay, how long should it take and how do I find out what's wrong and how to fix it?

Re-running pulumi up seems to be hanging again.

usuaally you'd get feedback right away, but in this case I suspect the docker provider is not working correctly. you can check if the image is being built and pushed using docker commands like `docker ps` and `docker images`

image.png

I've cleaned out all existing docker images, the pulumi up preview builds the image. Then the pulumi up gets stuck after reporting 'pushed'

And a second image is created with <http://nnnnnnnnnn.dkr.ecr.us-west-2.amazonaws.com/sampleapp-736f9e5|nnnnnnnnnn.dkr.ecr.us-west-2.amazonaws.com/sampleapp-736f9e5> which I assume is the image that is uploaded. I note that that's quite a large image that has to be uploaded. Is the sequence of events, that the image gets built locally and then uploaded to the aws repository? If it's a more than 1GB upload I can see that that would take a while to upload - is the hanging that it is uploading a large image?

it might be exactly that yes, it does get built locally

i'm still surprised it's taking 40+ minutes though

If that's the case is there anyway to see the upload progress?

And, if I update the docker image will it re-upload the full image or just the changes?

it should only push the changes, but this is managed by docker, not pulumi

i found delays of 15 minutes yesterday before things timed out and started to prefixing everything with  `pulumi refresh -y &amp;&amp;`  to get around the issue.