skip to Main Content

I am having this problem running Docker Compose on my machines. I have switched machines and the problem still persists.

Error Message:

[40335] Error loading Python lib '/tmp/_MEIR5kRcn/libpython3.7m.so.1.0': dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory

My OS is fully updated.

I have tried the solutions listed here, here and here.

Here is the output of ldd --version.

ldd (GNU libc) 2.35

Docker itself is functioning as expected. Docker-compose, however, isn’t. Trying to docker-compose up or docker-compose --version results in the error.

4

Answers


  1. I fix this issue by created a symbolic link from libcrypt.so to libcrypt.so.1

    Link this: $ ln -s /usr/lib/libcrypt.so /usr/lib/libcrypt.so.1

    Hope it’s worked for you

    Login or Signup to reply.
  2. install libxcrypt-compat maybe helps

    sudo pacman -S libxcrypt-compat
    

    https://archlinux.org/packages/core/x86_64/libxcrypt-compat

    Login or Signup to reply.
  3. This was my solution: delete directories ./build and ./dist and run pyinstaller again.

    I noticed that if ./build already exists, Pyistaller will reuse the same ./build. Any previous issues in ./build will persist, sometimes with new error messages, because the directory was not recreated. Deleting ./build leads to a new ./build being created next time you run pyinstaller.

    This was the original error I was getting.

    $ ./name_of_executable_created_by_pyinstaller 
    [26645] Error loading Python lib '/tmp/_MEITnO6JV/libpython3.7m.so': dlopen: /tmp/_MEITnO6JV/libpython3.7m.so: cannot open shared object file: No such file or directory
    
    Login or Signup to reply.
  4. I was running on manjaro. I had to remove docker-compose, install it back and symlink to it’s actual location. I don’t know if this works on other distros.

    sudo rm $(which docker-compose)
    

    Now install it back;

    sudo pacman -S docker-compose
    

    Finally create a symlink;

    sudo ln -s /usr/bin/docker-compose /usr/local/bin/docker-compose
    

    Confirm it’s fine;

    docker-compose --version
    
    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search