clever-egg-2543
02/03/2020, 2:27 PMpulumi
is not found. Yes, I’m updating my path:
=== Pulumi is now installed! 🍹 ===
+ Please add /root/.pulumi/bin to your $PATH
+ Get started with Pulumi: <https://www.pulumi.com/docs/quickstart>
$ export PATH=$PATH:$HOME/.pulumi/bin
$ which pulumi
/root/.pulumi/bin/pulumi
$ cd pulumi
$ pulumi login
/bin/sh: eval: line 96: pulumi: not found
mammoth-elephant-55302
02/03/2020, 2:31 PM/root/.pulumi/bin/pulumi
clever-egg-2543
02/03/2020, 2:32 PMwhich
finds it fine.mammoth-elephant-55302
02/03/2020, 2:32 PMclever-egg-2543
02/03/2020, 2:33 PMmammoth-elephant-55302
02/03/2020, 2:34 PM#!/bin/bash
# exit if a command returns a non-zero exit code and also print the commands and their args as they are executed
set -e -x
# Download and install required tools.
# pulumi
curl -fsSL <https://get.pulumi.com/> | bash
export PATH=$PATH:$HOME/.pulumi/bin
# Login into pulumi. This will require the PULUMI_ACCESS_TOKEN environment variable
pulumi login
# update the GitLab Runner's packages
apt-get update -y
apt-get install sudo -y
# nodejs
curl -sL <https://deb.nodesource.com/setup_8.x> | sudo -E bash -
apt-get install -y nodejs
# yarn
npm i -g yarn
clever-egg-2543
02/03/2020, 2:36 PM$ $(which pulumi) login
/bin/sh: eval: line 96: /root/.pulumi/bin/pulumi: not found
mammoth-elephant-55302
02/03/2020, 2:36 PM$
? It seems weird. usually shell prompt decorator for root user is #
clever-egg-2543
02/03/2020, 2:49 PMinstall:
stage: build
script:
- apk update && apk upgrade
- apk add --update --no-cache curl nodejs bash
- curl -fsSL <https://get.pulumi.com> | bash
- export PATH=$PATH:$HOME/.pulumi/bin
- cd pulumi
- pulumi login
- npm i
pulumi
is still not found.sh/bash
related. I’ve switched to bash, but have a new error:
=== Pulumi is now installed! 🍹 ===
+ Please add /root/.pulumi/bin to your $PATH
+ Get started with Pulumi: <https://www.pulumi.com/docs/quickstart>
+ cd pulumi
+ pulumi login
scripts/setup.sh: line 12: /root/.pulumi/bin/pulumi: No such file or directory
white-balloon-205
pulumi
issue - seems to be something odd about the environment you are running in? If which pulumi
is returning the correct thing, I have no idea why your shell would fail to exec pulumi
. Can you reproduce this outside of GitLab CI?clever-egg-2543
02/03/2020, 7:05 PMnode:dubnium-alpine3.10
image (to avoid trying to install node). I’m not suggesting that it’s a pulumi
issue, but it is an issue with the documentation, which I’ve been following.mammoth-elephant-55302
02/03/2020, 7:44 PMclever-egg-2543
02/03/2020, 7:52 PMroot
, but that appears to be the default. So, if root
installs it, shouldn’t root
be able to run it?white-balloon-205
.gitlab-ci.yml
: https://gitlab.com/rocore/demo-app/-/blob/master/.gitlab-ci.yml
• Dockerfile
: https://gitlab.com/rocore/global-infra/-/blob/master/base-image/Dockerfileclever-sunset-76585
02/04/2020, 3:19 AM.gitlab-ci.yml
file?run-pulumi.sh
for merge builds, because it is a demo project.clever-egg-2543
02/04/2020, 4:06 AMpulumi/pulumi
image specifically in the stages that require it. This causes me to rebuilt the npm
dependencies as the node version in the pulumi image is different from my target version. While it’s a bit of a hack to re-install the dependencies for each stage, the pipeline is now functional and each stage passes, so far.clever-sunset-76585
02/04/2020, 4:09 AM