Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volta error: Could not unpack Node #1546

Closed
happy-turtle opened this issue Aug 29, 2023 · 4 comments
Closed

Volta error: Could not unpack Node #1546

happy-turtle opened this issue Aug 29, 2023 · 4 comments

Comments

@happy-turtle
Copy link

happy-turtle commented Aug 29, 2023

Hello 👋 We are running Volta in a Github action runner and are experiencing frequent failures. This is getting so frequent that it requires retries every time and is not very much production ready. After a few retries it eventually runs fine though. Do you have any hints what the problem might be? The Volta installation runs fine, but it then fails on unpacking Node.

Run npm ci
  npm ci
  shell: /usr/bin/bash -e {0}
  env:
    VOLTA_HOME: /opt/hostedtoolcache/volta/1.1.1/x64
Volta error: Could not unpack Node v18.16.1

Please ensure the correct version is specified.
Volta error: Error cause: failed to unpack `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmpsOnC5r/node-v18.16.1-linux-x64/bin/node`

Error cause: failed to unpack `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmpsOnC5r/node-v18.16.1-linux-x64/bin/node`

Error cause: failed to unpack `node-v18.16.1-linux-x64/bin/node` into `/opt/hostedtoolcache/volta/1.1.1/x64/tmp/.tmpsOnC5r/node-v18.16.1-linux-x64/bin/node`

Error cause: Resource temporarily unavailable (os error 11)
Error: Process completed with exit code 126.

Edit: This was partially mentioned here already. But it looks more like an issue directly related to Volta.

@DerJacques
Copy link

We're running into the same issues. Two different machines on different networks, specifying different versions of node.
This has worked fine for us previously.

The node status page doesn't show any issues at the time of this message.

@yenshirak
Copy link

Same here.

@felipecrs
Copy link
Contributor

Duplicate of #1523.

@chriskrycho
Copy link
Contributor

Closing this as a duplicate of #1523. We are thinking about this problem, but none of us has yet had time to tackle it. See my latest comment there for our current best guesses as to what's going on!

@chriskrycho chriskrycho closed this as not planned Won't fix, can't repro, duplicate, stale Sep 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants