itzg / itzg/docker-minecraft-bedrock-server
Failed to open curl lib from binary, use libcurl.so instead
- Dominant language
- Shell
- Stars
- 1.9k
- Forks
- 303
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 2
Description
On Ubuntu Server 20.04, the latest Docker image containing server version 1.16.221.01 crashes after a few minutes of game play with the following log dump:
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.221.01
OS: Linux
Server start: 2021-05-01 14:42:52 UTC
Dmp timestamp: 2021-05-01 14:43:54 UTC
Upload Date: 2021-05-01 14:43:54 UTC
Session ID: 60f31624-d998-4de2-946c-8e56f72ca000
Commit hash: 29f5ac44317033b48a154d0e9ac51db5ce2d6805
Build id: 5873168
CrashReporter Key: 7ef34716-637f-3b3d-98e2-ef5690af7286
Crash
[INFO] at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead
Running the exact same server version (manually downloaded from https://www.minecraft.net/en-us/download/server/bedrock/) and installed on a different server running Ubuntu Server 20.04 but *NO DOCKER*, doesn't crash. According to https://bugs.mojang.com/browse/BDS-12695 perhaps you need to tweak the LD_LIBRARY_PATH setting in the Docker image?
See also https://bugs.mojang.com/browse/BDS-12751, although I think the ipv6 thing is a red herring.
(Judging by the mess that the last few Linux releases of the server software has been -- complier files included in the tarball, server executable not actually marked as executable -- I wouldn't be surprised if they've handed off the Linux port to some overworked unpaid intern in Hyderabad...)
Contributor guide
Research direction
No source file or test is named. Start by comparing the Docker image's library handling and LD_LIBRARY_PATH with the manually installed server on Ubuntu 20.04, using the reported libcurl message and linked BDS issues as context. Done means the containerized 1.16.221.01 server no longer crashes during gameplay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, ubuntu
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100