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

[arm64] Can't download the requested binary: Can't extract the file: failed to unpack #474

Closed
shirish87 opened this issue Jun 14, 2021 · 5 comments

Comments

@shirish87
Copy link

Unable to install most versions of node on an arm64 device.

OS: Ubuntu 18.04 LTS aarch64
Filesystem: ext4

Package xz-utils is installed. tar and xz are available.

image

Interestingly, v11.15.0 works fine.

image

v10 and v12 are failing on extracting an HTML doc file. Makes me wonder the source files were created with permissions preserved.

error: Can't download the requested binary: Can't extract the file: failed to unpack `/home/marvin/.fnm/node-versions/.downloads/.tmpY6gY1Q/node-v12.22.1-linux-arm64/lib/node_modules/npm/docs/public/cli-commands/npm-org/index.html`
@shirish87
Copy link
Author

Woops. nevermind, device was out of disk space 😞

@Schniz
Copy link
Owner

Schniz commented Jun 14, 2021

Thanks for fixing that yourself 😜

@palfrey
Copy link

palfrey commented Apr 6, 2023

I've just hit this on CircleCI, mostly because their XDG_RUNTIME_DIR is set to a 1.6GB tmpfs which apparently isn't enough. Is there any way to get better logging of this one? I'm not expecting the tool to be able to fix the problem, but just being able to say "hey, we ran out of disk here" would be really useful!

@palfrey
Copy link

palfrey commented Apr 6, 2023

I've just hit this on CircleCI, mostly because their XDG_RUNTIME_DIR is set to a 1.6GB tmpfs which apparently isn't enough. Is there any way to get better logging of this one? I'm not expecting the tool to be able to fix the problem, but just being able to say "hey, we ran out of disk here" would be really useful!

Having said this, I've spent an hour or so digging through this and trying to improve things and it's really hard right now. I suspect this will get better if rust-lang/rust#86442 eventually ever gets stabilised so then https://doc.rust-lang.org/std/io/enum.ErrorKind.html#variant.StorageFull appears.

@anerdwithaknife
Copy link

anerdwithaknife commented May 30, 2024

Not sure if I should open a new issue or add to this one since it was never actually resolved.

Just ran into this on WSL and it doesn't seem to be as straightforward as just diskspace.

My XDG_RUNTIME_DIR is set to /run/user/1000 and this is what the tmpfs mount points look like:

none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
none on /run/user type tmpfs (rw,relatime)

This is what df reports for free disk:

❯ df -h /run/user
Filesystem      Size  Used Avail Use% Mounted on
none             16G   84K   16G   1% /run/user

It still fails with the above error when I try to install Node 18.

However, pointing the XDG_RUNTIME_DIR env to a different folder (/tmp/foobar in my case) resolved it.

I'm on Windows 10 (64 bit) running Ubuntu 22.04.4 LTS in WSL.

Output from uname -a:

Linux WKS59536 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants