Library not loaded: @rpath/libarchive.13.dyli on M1 Mac #1826
Comments
|
can you send me your I would advise you to start from |
|
@wolfv , wow, that's a quick reply. Thank you. I don't think that |
|
I have installed |
|
|
|
@wolfv I've actually removed |
|
Also, I don't see |
|
interesting. It's definitely required for mamba, though. Do you have a new |
|
Sure, here is a new one |
|
i've experienced the same problem, and the hack proposed above works. |
|
Experienced the same problem, with the same solution. With the |
|
I was installing some specific packages for my environment |
|
Hi, I am getting a similar problem after upgrading mamba in the base env from 1.0.0 to 1.2.0. Traceback (most recent call last):
File "/Users/jovan/miniconda3/bin/mamba", line 7, in <module>
from mamba.mamba import main
File "/Users/jovan/miniconda3/lib/python3.8/site-packages/mamba/mamba.py", line 49, in <module>
import libmambapy as api
File "/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/__init__.py", line 7, in <module>
raise e
File "/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/__init__.py", line 4, in <module>
from libmambapy.bindings import * # noqa: F401,F403
ImportError: dlopen(/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/bindings.cpython-38-darwin.so, 0x0002): Library not loaded: @rpath/libarchive.13.dylib
Referenced from: <DC674B59-AD78-3A3E-9D76-D190B3490F4D> /Users/jovan/miniconda3/lib/libmamba.2.0.0.dylib
Reason: tried: '/Users/jovan/miniconda3/lib/libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/../../../libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/../../../libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/bin/../lib/libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/bin/../lib/libarchive.13.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS@rpath/libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/lib/libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/../../../libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/lib/python3.8/site-packages/libmambapy/../../../libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/bin/../lib/libarchive.13.dylib' (no such file), '/Users/jovan/miniconda3/bin/../lib/libarchive.13.dylib' (no such file), '/usr/local/lib/libarchive.13.dylib' (no such file), '/usr/lib/libarchive.13.dylib' (no such file, not in dyld cache)The hack of re-installing mamba and/or libarchive did not work.. Here is a my conda list if that helps Any advice short of re-installing everything? (I would not want to use my other environments.. ) Edit: downgrading mamba to 1.0.0 makes things work again. I might keep it like this until I am in a position to do a re-install.. |
|
If you're open to trying Micromamba: it doesn't have those kinds of problems. |
|
@jonashaag I am very open :). In fact I use micromamba docker for productionizing some projects. I would happily switch to either that or mambaforge as suggested by @wolfv when the current batch of projects wraps up.. |
|
Hi, I had the same issue on my M1 Mac when installing the latest mamba (1.3.1). As with @JovanVeljanoski, downgrading to 1.0.0 fixed the issue (did not try any of the versions in-between). |
|
I had the same problem and tried method of @kdubovikov but the problem still exists. Then tried the answer from here and successed: |
|
Neither the libarchive install hacks work for me on my M1. I basically have just given up on using mamba for the last six months rather than spend many more hours experimenting with how to fix this. ;-( |
|
I finally had some time in between projects, just reinstalled conda, reinstalled mamba, and had my environments all up and running with no problems in 10 mins (multiple environments). No problems. Probably reinstalling your conda/mamba env every 1-2 years is not that bad of an idea.. |
|
I have a relatively new Mac M1 machine and set it up 6 months ago. There is a limit to how many experimental installs I am willing to do to work around bugs. The fact is that the mamba distribution is currently broken on the M1. It really should not be depending on files from outside the conda environment that might not exist or may not be compatible. The M1 is a relatively new architecture, so it probably will still take a while before it gets supported routinely. :-( |
|
Same problem on M2 Mac. Installing libarchive via conda worked for me. |
Worked for me. thanks! |
I couldn't get any of the suggested fixes in these threads to work, so I switched to |
|
I experienced the same error on an x86 Mac, but my libarchive was actually installed so |
|
I had a very similar issue on my new M2 MacBook Pro. I found that a number of conda packages were not appearing for me in
However, upon installing one of the desired tools, I had the same sort of "Library not loaded" as described by OP. After some frustration, I realized that there is a very simple solution. First, I noticed that my
|
|
Just so it doesn't get lost somewhere in the thread: Micromamba shouldn't have those problems, try that! |
|
same problem while building a Docker container: I added this after installing mamba before running mamba --version and I also added apt-get update & upgrade to the top of the Dockerfile, now everything seems to work... |
|
I ran into an error that might be related to this. On another machine I am running miniconda 23.1.0 in combination with mamba and it works perfect (and also did for a long time). So, I did the same on this machine and clean uninstalled miniconda 23.5.2 and replaced it with miniconda 23.1.0 and reinstalled mamba and now it works. There seems to be an incompatibility of mamba with the newest version of miniconda. Can anyone confirm this? |
|
I have From building this Dockerfile https://github.com/Ouranosinc/PAVICS-e2e-workflow-tests/blob/cb53fec969539440269b313d8424dd436451269d/docker/Dockerfile#L1-L9
I am on Linux, not Mac but this is the only issue about libarchive.13 currently open so I thought I would centralize all the info here. |
|
Don't mix conda-forge and defaults |
With the ordering I used, conda-forge should have precedence over defaults. |
|
I did |
|
|
just do: mamba install pysqlite3 (or conda) |
|
I am sporadically seeing something very similar in the conda-lock CI, e.g. here It's hard to tell exactly which command is being run, so I added So I think it originates from when I use the explicit-type lockfile. It seems a bit odd to me that the exit code is 134 (SIGABRT), but maybe that's normal for libraries not found? I will report back once I get more info. I wonder if it's something like an edge case where there's somehow an extra dependency not covered by the lockfile and it mixes with |
|
On conda-forge, On The problem is likely due to mixing channels (e.g. @maresb: the problem that you describe is rather due to For now, I'll close this issue. If someone observes the problem again, I would recommend that they provide a reproducer. |
|
Just leaving this here after a grueling grind on a MBP Sanoma with M3. What eventually made the torture stop: |
and others
Any mamba command results in the following error for me. I use a M1 Macbook and a fresh miniconda installation. Mamba was installed using
conda install mamba -n base -c conda-forge.The text was updated successfully, but these errors were encountered: