pulumi: pulumi install for linux does not work
this happened during a usability study today…
Hello, I just tried running the install pulumi script for Linux I found at https://www.pulumi.com/docs/get-started/aws/begin/
curl -fsSL https://get.pulumi.com/ | sh
but got the following error while extracting the file:
=== Installing Pulumi v3.33.1 ===
+ Downloading https://get.pulumi.com/releases/sdk/pulumi-v3.33.1-linux-x64.tar
% Total % Received % Xferd Average Speed Time Time Time Curren
Dload Upload Total Spent Left Speed
100 78.7M 100 78.7M 0 0 9856k 0 0:00:08 0:00:08 --:--:-- 10.2M
+ Extracting to /home/max/.pulumi/bin
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
We're sorry, but it looks like something might have gone wrong during installa
If you need help, please join us on https://slack.pulumi.com/
https://get.pulumi.com/releases/sdk/pulumi-v3.33.1-linux-x64.tar does not exist
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 29 (16 by maintainers)
@AaronFriel I think I finally figured out what’s going on here and it has nothing to do with Pulumi. It turns out that attached file is actually just an empty file (
curlwasn’t saving the data to the output file in the/tmp/directory). I’m not sure why, but snapcurlseems to have issues writing to output files in various types of directories (as an example see: https://askubuntu.com/questions/1356327/cant-write-to-a-hidden-path-using-curl).In case anyone runs into this issue in the future, the resolution for me was the solution documented in the linked thread:
The Pulumi install script should work just fine afterwards with apt
curlinstalled.this worked for me. 😃 thank you
just ducking back in to say it is wild to me that the issue was curl being installed via snap instead of apt on my machine (apparently). very impressed with the digging @nhobin219!
Could you upload that tar.gz to Google Drive/Dropbox/etc and share a link with me?
At the same time, what’s the sha256sum of it? It should be:
db0154d8866b0a4dfc3dae4bb67211c291e4ed3ac729376bbfa0f5c231d72ed3
That’s what our GitHub release has and I’ve just checked by pulling the tarball and that’s what I got. What I don’t understand is why some folks might be getting incomplete or invalid tars.
Apologies for the unhelpful comment lol. I didn’t dig too much into it, but let me go ahead and run the commands from the above thread and see if I can get any useful information. I will post back here in a bit.
I ended up manually installing using the linux binary with no issues.
Just as an FYI, I experienced this exact same issue on
Ubuntu 22.04.1 LTS. The Linux install command does not work for me.@MaxPowerWasTaken to try to get you going sooner with Pulumi, please try this minimal install script as well:
per @dixler’s request in slack [UPDATED]…