This message was deleted.

You should in general get plugins as part of running

npm install

(or equivalent). In general, you should not need to run

pulumi plugin install

. Curious: 1. Are you using JS/TS or Python? 2. Did you run

npm install

or similar? And did it succeed? 3. What OS are you on? 4. What does

pulumi plugin ls

show you? To unblock, you should be able to just run

pulumi plugin install resource docker 0.17.0

.

running

pulumi plugin install resource docker 0.17.0

did indeed solve it 🙂 to answer your questions: 1) Go 2) The go get for pulumi-docker didn't work and threw an error (

cannot use (*Provider)(nil) (type *Provider)...

) 3) macOS Mojave 4) it didn't have anything before, but now it shows the docker plugin and my docker container runs

1) Go

Ahh - indeed - this process is not automated for Go. This is tracked in https://github.com/pulumi/pulumi/issues/1549. Any Go example/tutorial should include the explicit mention of this required step. Curious which one you were using that missed this?

1) I was looking at the https://github.com/pulumi/examples/tree/master/aws-go-s3-folder and trying to see if I could rebuild my own stack using Pulumi (which now seems to be going pretty good). It didn't mention any installs of plugins, so I could have missed it. 2) my bad... typo in the command 😓

Great - thanks - fixed that example up: https://github.com/pulumi/examples/commit/4ebf1db4c7bed80d5757dddf86561f86188940dc

thank you 😄 🙏