beammp-server: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

RouHim / beammp-container-image

A container image to run a BeamMP server.

GNU General Public License v3.0

48 stars 11 forks source link

beammp-server: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory #14

Closed asamson23 closed 2 years ago

asamson23 commented 2 years ago

When attempting to run the docker container with the updated image for BeamMP, there is the error when attempting to run the docker container

RouHim commented 2 years ago

Hey @asamson23, thank you for the bug report. I'll have a look and keep you updated.

Which container runtime, operating system and platform do you use?

asamson23 commented 2 years ago

The container is running under Docker version 20.10.14 on Unraid 6.10.3.

asamson23 commented 2 years ago

As for the image of the executable, I took the one available on the official website

RouHim commented 2 years ago

Can you please pull the latest image and try again?

asamson23 commented 2 years ago

Latest beammp-server image or latest docker image?

RouHim commented 2 years ago

latest container image

asamson23 commented 2 years ago

The server was updated to the latest version and that's when the issues started to happen. The server is updated and was force updated to the latest version.

RouHim commented 2 years ago

Sorry I do not get your point, what do you exactly do? Can you please describe it step by step.

asamson23 commented 2 years ago

Under the Docker tab in Unraid, under "Advanced view", there is a "force update" button to force a fetch from the Docker hub. As for the executable, I went to the official website, grabbed the zip file, extracted the linux version and renamed it to "beammp-server"

RouHim commented 2 years ago

Ok it looks like unraid does not understand the new oci metadata format. Ok good hint, I'll set it to docker to be backwards compatible.

RouHim commented 2 years ago

I fixed it. If this pipe is done: https://github.com/RouHim/beammp-container-image/actions/runs/2862630418 you should pull the latest docker container image.

asamson23 commented 2 years ago

I pulled the latest image build once it got pushed on the docker hub, but I still get the same issue

RouHim commented 2 years ago

Ok, I lets have another try: https://github.com/RouHim/beammp-container-image/actions/runs/2862809638 Looks like openssl 1.1 is missing (Only 3) in 22.04

RouHim commented 2 years ago

Btw your mount point looks fishy, why do you mount the whole server folder to your host? If you want to install mods, only mount the beammp/Resources/Client to your host.

asamson23 commented 2 years ago

Ok, I lets have another try: https://github.com/RouHim/beammp-container-image/actions/runs/2862809638 Looks like openssl 1.1 is missing (Only 3) in 22.04

That fixed it!

Btw your mount point looks fishy, why do you mount the whole server folder to your host? If you want to install mods, only mount the beammp/Resources/Client to your host.

As for the mount point on the host, it is the only way for me to be able to access the ressource folder so that I can load up mods on my server

RouHim commented 2 years ago

Yeah :) Great. But as I said, it's best to mount as less as possible, as described above only the client mods folder.

check the example docker compose file: https://github.com/RouHim/beammp-container-image/blob/main/docker-compose.yml

Otherwise you could mess up your permissions.