I'm trying out the example aws-ts-lambda-thumbnailer. pulumi up seems to get stuck and just sits there for a considerable amount of time. How long should I wait for it before giving up? How long would it normally take to do a pulumi up for this example? Is there a way to see what's going on so I know if it is hanging or if it is actually doing something? (The example in the readme with the repo shows a duration of 1m41s - mine is running for more than 40 minutes). The only difference I have is that the docker container won't build with a error: The command '/bin/sh -c mv ffmpeg-4.3.1-amd64-static/ffmpeg /usr/bin' returned a non-zero code: 1. So I replaced RUN "mv ffmpeg-4.3.1-amd64-static/ffmpeg /usr/bin" with "RUN mv ffmpeg-*-amd64-static/ffmpeg /usr/bin"

it shouldn't take 40 minutes 😞 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?

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

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

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

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

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

Okay, understood. Thanks for your help.

i found delays of 15 minutes yesterday before things timed out and started to prefixing everything with

pulumi refresh -y &&

to get around the issue.