This message was deleted.

sparse-intern-71089

10/15/2020, 10:15 PM

This message was deleted.

ambitious-appointment-66307

10/15/2020, 10:16 PM

I’m getting error: no stack selected; please use

pulumi stack select

pulumi stack init

to choose one when running

pulumi preview

ambitious-appointment-66307

10/15/2020, 10:17 PM

pulumi ls

shows me an empty table + pulumi stack ls NAME LAST UPDATE RESOURCE COUNT URL

ambitious-appointment-66307

10/15/2020, 10:17 PM

but when I ls the dir, I see the stack files

Copy code

+ ls -la
total 64
drwxrwxrwx 5 root root 4096 Oct 15 21:45 .
drwxrwxrwx 4 root root 4096 Oct 15 10:17 ..
drwxrwxrwx 6 root root 4096 Oct 15 21:44 .git
-rw-rw-rw- 1 root root 4071 Oct 15 10:17 .gitignore
-rw-rw-rw- 1 root root  864 Oct 15 21:20 .gitlab-ci.yml
-rwxrwxrwx 1 root root  171 Oct 15 10:17 Pulumi.prod.yaml
-rwxrwxrwx 1 root root  118 Oct 15 10:17 Pulumi.yaml

ambitious-appointment-66307

10/15/2020, 10:18 PM

I’m running a local gitlab-runner with the docker executor

ambitious-appointment-66307

10/15/2020, 10:18 PM

and I couldn’t see any reference to which image to use, so I’m just using the

pulumi/pulumi-base

image

little-cartoon-10569

10/15/2020, 10:19 PM

Are you mounting the correct host directory or volume?

little-cartoon-10569

10/15/2020, 10:19 PM

You can use a language-specific one, I use pulumi/pulumi-nodejs

ambitious-appointment-66307

10/15/2020, 10:19 PM

okay, good to know

ambitious-appointment-66307

10/15/2020, 10:19 PM

I can see the files if I

ls

- so I assume gitlab runner is doing the correct thing

little-cartoon-10569

10/15/2020, 10:20 PM

Have you used

pulumi login

ambitious-appointment-66307

10/15/2020, 10:20 PM

yep, that works fine

ambitious-appointment-66307

10/15/2020, 10:20 PM

Copy code

+ pulumi login
Logging in using access token from PULUMI_ACCESS_TOKEN
Logged in to <http://pulumi.com|pulumi.com> as limx0 (<https://app.pulumi.com/limx0>)

ambitious-appointment-66307

10/15/2020, 10:21 PM

I noticed the setup script installs pulumi - but if I am using the docker image, I assume I can skip this step

ambitious-appointment-66307

10/15/2020, 10:21 PM

maybe that’s whats messing it up

little-cartoon-10569

10/15/2020, 10:22 PM

It works from pulumi/pulumi-nodejs. I'll see what's in pulumi/pulumi-base...

ambitious-appointment-66307

10/15/2020, 10:22 PM

okay - I’m using the python sdk, let me change images

little-cartoon-10569

10/15/2020, 10:23 PM

You need to install the SDK yourself, according to the image docs: https://hub.docker.com/r/pulumi/pulumi-base

little-cartoon-10569

10/15/2020, 10:24 PM

So you might be better off switching to pulumi/pulumi-python

ambitious-appointment-66307

10/15/2020, 10:24 PM

okay good pick up

ambitious-appointment-66307

10/15/2020, 10:25 PM

and then assuming I’m running this image, can I confirm I should need any of the nodejs/npm/yarn libraries?

ambitious-appointment-66307

10/15/2020, 10:25 PM

would you expect something like this to just work?

Copy code

# pulumi-preview.sh
pulumi login
pulumi preview

little-cartoon-10569

10/15/2020, 10:27 PM

No, you need to add

pulumi stack select prod

in the middle.

little-cartoon-10569

10/15/2020, 10:27 PM

Unless you're using an organization, in which case,

pulumi stack select yourorg/prod

ambitious-appointment-66307

10/15/2020, 10:27 PM

okay no problem

ambitious-appointment-66307

10/15/2020, 10:28 PM

Thanks for the help @little-cartoon-10569

ambitious-appointment-66307

10/15/2020, 10:28 PM

hmm still not seeing it

little-cartoon-10569

10/15/2020, 10:28 PM

About the npm dependencies from python: does requirements.txt resolve this?

ambitious-appointment-66307

10/15/2020, 10:29 PM

I’m not sure - but it seems to be running as expected

little-cartoon-10569

10/15/2020, 10:29 PM

Have you got it workign using the docker image, but locally instead of from GitLab-CI?

ambitious-appointment-66307

10/15/2020, 10:29 PM

nope, so my issue is basically, pulumi in a docker image doesnt recognise the files I’m mounting

ambitious-appointment-66307

10/15/2020, 10:29 PM

in the current dir

little-cartoon-10569

10/15/2020, 10:30 PM

I use the docker image locally. I need 3 mounts to get docker to see the right stuff:

~/.pulumi:~/.pulumi

~/.aws:~/.aws

, and

.:/pulumi/projects

ambitious-appointment-66307

10/15/2020, 10:30 PM

ahhhh okay

ambitious-appointment-66307

10/15/2020, 10:31 PM

so something in .pulumi is probably missing

ambitious-appointment-66307

10/15/2020, 10:31 PM

is there a way to somehow generate that from an existing project via a token/Pulumi.yaml files ?

ambitious-appointment-66307

10/15/2020, 10:32 PM

can I do a

pulumi stack init

or something? That way I wouldnt have to build a totally sepaarete docker image for my CI

little-cartoon-10569

10/15/2020, 10:32 PM

I think it mightn't be needed from a pipeline because you're logging in each time. Env vars are used, there's no continuity expected from run to run.

little-cartoon-10569

10/15/2020, 10:32 PM

But if you're running from docker locally, and expecting it to work as if it was running on your host machine, you need these things.

ambitious-appointment-66307

10/15/2020, 10:32 PM

thats what I would have thought

ambitious-appointment-66307

10/15/2020, 10:33 PM

I’m also logging in locally via env variable

little-cartoon-10569

10/15/2020, 10:33 PM

So you might try getting it working locally in Docker, to see if you can reproduce the issue, just in case it's not environmental: maybe your yaml files are broken...?

ambitious-appointment-66307

10/15/2020, 10:33 PM

(basically exactly what gitlab would be doing)

ambitious-appointment-66307

10/15/2020, 10:33 PM

okay I’ll keep trying, thanks very much for your help

little-cartoon-10569

10/15/2020, 10:34 PM

Good luck. Hopefully someone else with GitLabCI-specific knowledge will pop in to the thread soon 🙂

ambitious-appointment-66307

10/15/2020, 10:45 PM

okay - the solution was just to call

- pulumi stack init prod || true

again

ambitious-appointment-66307

10/15/2020, 10:45 PM

(it fails as the files already exist, but thats enough to allow pulumi cli to see it)

ambitious-appointment-66307

10/15/2020, 10:45 PM

which is probably creating the

~/.pulumi

dirs

little-cartoon-10569

10/15/2020, 10:46 PM

Ah. Clever.

2 Views

Open in Slack

Previous Next

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.