Are there any gotchas for containerizing applications that run the Automation API? I'm running into some interesting behavior when spinning up an ECS stack when ran locally vs. inside of the container. Specifically, an AWS error related to the fargate service I'm spinning up.

Error: The default VPC does not have any private subnets. Set `assignPublicIp` to `true`, provide `networkConfiguration`, or add private subnets to the default VPC

Are you sure you're running pulumi w/ same aws account/user/role/region between your local environment vs. within container?

Yes, I'm passing the same .env file using

--env-file

@few-carpenter-12885 I think I am doing something similar, what does your dockerfile look like that it was able to install pulumi successfully?

I think the error was legitimate. My stack was trying to deploy to the default VPC as private. Resolved it.

@few-carpenter-12885 you are not using the pulumi based image and you are able to import pulumi into your project on the ecs task?

Ah, sorry, yeah I'm using the pulumi-nodejs image as the base.

@few-carpenter-12885 if you don't mind me asking, are you using an s3 backend?

No, I'm using the default backend

ah, ok, thank you!