ruby example fails during build (waypoint up) Installing node-v12.16.2-linux-x64 about waypoint-examples HOT 4 CLOSED

I was not able to reproduce this issue, however I am on Ubuntu 20.04 so it may be something that is present on Mac/Docker. What version of Docker Desktop are you running? Does a system/volume prune help at all?

from waypoint-examples.

Hello,

Thank you for your response.

I no longer believe this is an issue with waypoint-examples specifically but rather with the archive files being downloaded during the build process - in particular the node archive.

The specific failure (for me) can be reproduced if we invoke the curl for node directly like so:

curl -L --fail --retry 5 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3.amazonaws.com/heroku-nodebin/node/release/linux-x64/node-v12.16.2-linux-x64.tar.gz -s -o node-v12.16.20-linux-x64.tar.gz

I get a gzipped file on my local filesystem which, when I attempt to decompress it, results in:

tar zxvf node-v12.16.2-linux-x64.tar.gz 
x node-v12.16.2-linux-x64/
x node-v12.16.2-linux-x64/bin/
x node-v12.16.2-linux-x64/bin/node: truncated gzip input
tar: Error exit delayed from previous errors.

It's possible the archive is not being downloaded correctly and the unzip portion of the pipe is failing - leading to the build-stage failure.

If I download the tarball using my chrome-browser I can unpack it perfectly well. Something about the download in the context of the waypoint build is resulting in a malformed archive download.

Is there a way for me to add some verbosity or debugging to that particular stage of the build ?

EDIT:

I am using Docker desktop v3.3.3 (64133).
volume pruning does not alter the behaviour.

from waypoint-examples.

You can use bash verbosity flags with any Waypoint command (e.g. waypoint build -vvv), which will give surrounding Waypoint context but I don't think it will help dive into this issue.
The pack builder uses buildpacks/pack to run the build (see here)
This may be an upstream issue there.

from waypoint-examples.

Hey there @sven-agnew - for now, I recommend adding any additional context to the upstream Waypoint repo. We have an issue currently tracking this over there: hashicorp/waypoint#1826

I don't think this is an issue with the example project itself, so it would be best to move the conversation over there. Thank you!

from waypoint-examples.