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

image.png

Strange, because pulumi thinks it only ran for 12s

Seems to be an issue of running pulumi inside a container?! Only started happening after I started with the migration process though.

With latest `3.21.1` CLI a simple `pulumi up` is now taking over 10 minutes.

I just ran `pulumi preview -d &gt; debug.txt` happy to send that to someone. <@UB3BGTV63> who could look at this?
I can't run `pulumi up` with debug mode, because it requires me to supply `--yes` to it as well, which I don't want to do now.
Even the preview took almost 4 minutes now, which seems very long.

The logs that would be useful are these: <https://www.pulumi.com/docs/troubleshooting/|https://www.pulumi.com/docs/troubleshooting/>. The perf traces there would be particularly useful. 

Feel free to DM me and I'll open an issue to track whatever appears to be underlying problem.  

Are you seeing reliably different results with different CLI versions in the same environment?

Certainly a different environment could have more limited memory or bandwidth, or could have very slow disk, which could impact performance. 