This message was deleted.
# generals
sparse-intern-71089
07/03/2019, 12:52 PMThis message was deleted.
c
clever-sunset-76585
07/03/2019, 4:14 PMYou can use the Docker image if that works better for you. The scripts were used to demonstrate setting up the CLI and other tools relevant to the stack you are working with (i.e. the NodeJS runtime). Using the script allows you to control what tools you install in your CI environment. But if you don’t care about that, you could simply use the Docker image, which installs quite a few things.
a
ambitious-van-68615
07/04/2019, 7:42 AMOk I see the idea thanks 😁
ambitious-van-68615
07/04/2019, 7:49 AM(My2cts) I would rather write the guide using this all-inclusive Docker image, and then describe what's inside, as it's kind of a walkthrough and people might use it as it is (and then there would be more running things and more complexity). But I get it
ambitious-van-68615
07/05/2019, 3:26 PMFollowing this thread : I can't figure out how to execute a simple
cd dirENTRYPOINT ["pulumi"]m
millions-judge-24978
07/05/2019, 7:31 PMYou would either need to override the entrypoint when running the image, or use this parameter to
pulumi-C, --cwd string Run pulumi as if it had been started in another directorymillions-judge-24978
07/05/2019, 7:36 PMfor example,
docker run -it --rm --entrypoint=/bin/sh pulumi/pulumia
ambitious-van-68615
07/05/2019, 9:41 PMI will try your advise, thank you !
ambitious-van-68615
07/09/2019, 12:24 PMFor those who might search for a solution some day : using Gitlab CI, you should override the entrypoint using the
image:entrypoint3 Views