dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory

Question

I use EndeavourOS and have updated my system on February 17 2022 using

sudo pacman -Syu

Eversince, when I run docker-compose, I get this error message:

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

Some forum threads suggested to reinstall docker-compose, which I did. I tried the following solution, but both without success:

Python3.7: error while loading shared libraries: libpython3.7m.so.1.0

How can I resolve this issue?

score 56 · Answer 1 · answered Mar 13 '22 at 10:37

56

Install libxcrypt-compat from pacman (Official Repositories)

answered Mar 13 '22 at 10:37

long-blade

721
1
5
9

score 17 · Answer 2 · edited Feb 21 '22 at 16:13

17

Same thing happened to me today, this is what I did to fix it (Arcolinux 5.16.10-arch1-1)

Removed docker-compose

$ sudo rm -r /usr/local/bin/docker-compose

Reinstalled it using pip (was not working with the curl method)

$ sudo pip install docker-compose

edited Feb 21 '22 at 16:13

Dharman

30,962
25
85
135

answered Feb 21 '22 at 16:08

dam0ne

179
2

3

Note this installs old (v1) version of `docker-compose`, while the one being currently developed is v2. Also, manually removing binaries is definitely NOT a recommended way of removing software from any Linux-based system. – Maks Babarowski Feb 23 '22 at 22:55
2

@MaksBabarowski: Thank you! I had V1 installed before, so it is suitable for the time being. Docker suggests in their docs to uninstall by remove binaries manually. – T_Torture Feb 26 '22 at 19:59

score 15 · Answer 3 · edited Dec 14 '22 at 19:36

15

I use Arch Linux and it worked for me:

 # cd /usr/lib
 # sudo ln ./libcrypt.so libcrypt.so.1
 # docker-compose -v

 docker-compose version 1.29.2, build 5becea4c

edited Dec 14 '22 at 19:36

Matthias Braun

32,039
22
142
171

answered Feb 24 '22 at 16:30

Lindomar

167
5

score 3 · Accepted Answer · answered Jun 09 '22 at 16:20

The underlying issue here is that you use docker-compose instead of docker compose, which are two different binaries. docker-compose is also known as V1, and is deprecated since April 26, 2022. Since then, it does not receive updates or patches, other than high-severity security patches.

So, to fix your issue, use docker compose instead of docker-compose. If you compare docker compose version and docker-compose version, you will see that this uses the newer docker compose and runs without an issue.

score 2 · Answer 5 · answered Feb 19 '22 at 22:27

I found several forum posts explaining to isntall libxcrypt-compat from AUR. I did not like this solution, but apparently, this is the way for now: https://bbs.archlinux.org/viewtopic.php?id=274160&p=2

If there is a PGP key error when building the package from AUR, use this workaround as explained by Stock44 on this page: https://aur.archlinux.org/packages/libxcrypt-compat

$ gpg --keyserver keyserver.ubuntu.com --recv-key 678CE3FEE430311596DB8C16F52E98007594C21D

_{Posted on behalf of the question asker}

It's in official repos as well. `pamac install libxcrypt-compat` did the job for me. — Rafał G., Feb 27 '22 at 18:13

dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory

5 Answers5