mamba: wget: Micromamba Download link is corrupted
Troubleshooting docs
- My problem is not solved in the Troubleshooting docs
How did you install Mamba?
Micromamba
Search tried in issue tracker
Latest version of Mamba
- My problem is not solved with the latest version
Tried in Conda?
Not applicable
Describe your issue
Attempting to install micromamba via download link fails.
wget -qO- http://micromamba.snakepit.net/api/micromamba/linux-64/latest | tar -xvj bin/micromamba
(same bug happens with https url) output:
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
however…
"${SHELL}" <(curl -L micro.mamba.pm/install.sh)
does work!
mamba info / micromamba info
No response
Logs
No response
environment.yml
No response
~/.condarc
No response
About this issue
- Original URL
- State: open
- Created 7 months ago
- Reactions: 1
- Comments: 18 (1 by maintainers)
Commits related to this issue
- Fix: Docker build fails with bzip2 error Details can be found at https://github.com/mamba-org/mamba/issues/2998 — committed to oschwengers/bakta by lukasjelonek 7 months ago
After a look to the
wgetman-page I found another option:This may be another option to get rid of the conversion.
Eventually the download server that generates the s3-download-links should report the correct encoding in its response, so that users won’t need to override it manually.
I found the solution for me:
wget --no-iri -qO- https://micromamba.snakepit.net/api/micromamba/linux-64/latest | tar -xvj bin/micromambaThe
--no-irioption disables the uri-conversion as a side-effect and the download works again.replicable in a debian container on my machine.
curlthe url has the same error