This message was deleted.
# generals
sparse-intern-71089
09/30/2020, 2:09 AMThis message was deleted.
l
little-cartoon-10569
09/30/2020, 2:18 AMIt has happened sporadically to me. Sometimes it's because there's two dependencies on the plugin, sometimes it just gets confused. Are you volume/bind mounting your ~/.pulumi directory? If you're using different home directories at different times then you may confuse Pulumi.
little-cartoon-10569
09/30/2020, 2:22 AMAnd if you are bind-mounting and the .pulumi directory has the wrong owner, that can also cause problems.
h
hundreds-egg-46465
09/30/2020, 2:27 AMIm using it as a base image and extending from it within the dockerfile.
Your comment about the two dependencies thing has given me something to look into however
l
little-cartoon-10569
09/30/2020, 2:28 AMAre you aware of the language-specific images?
little-cartoon-10569
09/30/2020, 2:28 AMMuch smaller
h
hundreds-egg-46465
09/30/2020, 2:41 AMYeah but ive had issues with them in the past but might try it out to see if it fixes this issue.
hundreds-egg-46465
09/30/2020, 4:57 AMFYI i fixed this issue, still not 100% sure but its something to do with the stack not being deployed at all yet and running it in the docker container which means that the 'state' (output of
pulumi stack exportb
billowy-army-68599
09/30/2020, 2:25 PM
This is interesting insight, which language were you using?
h
hundreds-egg-46465
10/01/2020, 1:25 AMtypescript, after discussing internally I have a feeling it may be due to how npm install is being run so going to try another fix today
hundreds-egg-46465
10/01/2020, 2:59 AMok yeah, so the root causes was not running npm install in the main pulumi image inside the dockerfile (since we were using a multistage build) which meant the aws provider wasn't installed and then since it wasnt listed in the "state" it didnt install at runtime and so just failed.
tldr; needed to run
npm install👍 1
2 Views