bedrock server not starting GLIBCXX_3.4.26 not found

[555wolfman]

i can't start any docker bedrock containers. running it interactive it shows following error message and stops within 3 seconds

./bedrock_server-1.20.30.02: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.26' not found (required by ./bedrock_server-1.20.30.02) ./bedrock_server-1.20.30.02: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.29' not found (required by ./bedrock_server-1.20.30.02)
./bedrock_server-1.20.30.02: /lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_2.30' not found (required by ./bedrock_server-1.20.30.02)

Assuming it coul'd have been on my host, i upgraded it from debian 10 to debian 11 but still the same error.
So i think the linux image used by the container uses an old gcc library.

do you need to update the container image, or is there an old image on my docker image cache?

[555wolfman]

I just pulled the latest versions of all my docker images / cache - the problem still exists

[555wolfman]

On the official site there is a mention to change the LD_LIBRARY_PATH:
which is a suggestion i found for different applications having a similar error message

https://www.minecraft.net/en-us/download/server/bedrock

MINECRAFT DEDICATED SERVER SOFTWARE FOR UBUNTU (LINUX)
Unzip the container file into an empty folder. Start the server with the following command:

LD_LIBRARY_PATH=. ./bedrock_server

Follow the bundled how to guide to configure the server.

[555wolfman]

Hmmm. in bedrock-entry.sh in line 188

export LD_LIBRARY_PATH=.

Could it be on Mojang's side?

Maybe as temporary fix set LD_LIBRARY_PATH to Debians:
/usr/lib/x86_64-linux-gnu/
?

[bollowatsch]

I have the same issue, did you manage to resolve it or work around it?

[itzg]

The latest image starts fine for me:

> docker pull itzg/minecraft-bedrock-server
Using default tag: latest
latest: Pulling from itzg/minecraft-bedrock-server
Digest: sha256:6eef6a521647a2bcb08b71d13d3d49c37021e0f4f2f4e701966dd8be4a976ce2
Status: Image is up to date for itzg/minecraft-bedrock-server:latest
docker.io/itzg/minecraft-bedrock-server:latest

What's Next?
  View a summary of image vulnerabilities and recommendations → docker scout quickview itzg/minecraft-bedrock-server
> docker run -it --rm -e EULA=true itzg/minecraft-bedrock-server
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
Looking up latest version...
Downloading Bedrock server version 1.20.31.01 ...
Starting Bedrock server...
NO LOG FILE! - setting up server logging...
[2023-09-29 13:05:04:903 INFO] Starting Server
[2023-09-29 13:05:04:903 INFO] Version: 1.20.31.01
[2023-09-29 13:05:04:903 INFO] Session ID: e90501ab-3fd8-4214-a5f1-fd54fb96665b
[2023-09-29 13:05:04:903 INFO] Build ID: 18258844
[2023-09-29 13:05:04:903 INFO] Branch: r/20_u3
[2023-09-29 13:05:04:903 INFO] Commit ID: ac4488fb62a797cb4fa23e49918006e331db5c08
[2023-09-29 13:05:04:903 INFO] Configuration: Publish
[2023-09-29 13:05:04:903 INFO] Level Name: Bedrock level
[2023-09-29 13:05:04:904 INFO] No CDN config file found for dedicated server
[2023-09-29 13:05:04:904 INFO] Game mode: 0 Survival
[2023-09-29 13:05:04:904 INFO] Difficulty: 1 EASY
[2023-09-29 13:05:04:905 INFO] Content logging to console is enabled.
[2023-09-29 13:05:04:133 INFO] Opening level 'worlds/Bedrock level/db'
[2023-09-29 13:05:05:525 INFO] IPv4 supported, port: 19132: Used for gameplay and LAN discovery
[2023-09-29 13:05:05:525 INFO] IPv6 not supported
[2023-09-29 13:05:05:529 INFO] Server started.
[2023-09-29 13:05:05:529 INFO] ================ TELEMETRY MESSAGE ===================
[2023-09-29 13:05:05:529 INFO] Server Telemetry is currently not enabled.
[2023-09-29 13:05:05:529 INFO] Enabling this telemetry helps us improve the game.
[2023-09-29 13:05:05:529 INFO]
[2023-09-29 13:05:05:529 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[2023-09-29 13:05:05:529 INFO] to the server.properties file in the handheld/src-server directory
[2023-09-29 13:05:05:529 INFO] ======================================================

What is your host kernel version and CPU architecture? I'm hoping you all will find some common pattern external to the image that is influencing the failure.

[bollowatsch]

OS: linux x86_64 Debian GNU/Linux 11 (bullseye)
Kernel: 5.15.107-2-pve

OS is up to date

[555wolfman]

Thanks for your help, i got it to run.

What worked for me:

1. docker pull
2. docker rm (My container, my named volume is not removed)
3. docker run (Refering to my still existing named volume)