https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
You 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
Ok I see the idea thanks 😁
(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
Following this thread : I can't figure out how to execute a simple 
cd dir
using this official CLI Docker image, possibly due to the 
ENTRYPOINT ["pulumi"]
in the associated Dockerfile 😔 I get `Error: unknown command "sh" for "pulumi"``
m
You would either need to override the entrypoint when running the image, or use this parameter to 
pulumi
if it fits your use case: 
-C, --cwd string                   Run pulumi as if it had been started in another directory
for example, 
docker run -it --rm --entrypoint=/bin/sh pulumi/pulumi
locally will give you a shell into the container
a
I will try your advise, thank you !
For those who might search for a solution some day : using Gitlab CI, you should override the entrypoint using the 
image:entrypoint
option
2 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by