Fails to start in docker with latest ValheimPlus (0.9.17.0)

[LongerHV]

Valheim server in docker fails to start with the latest ValheimPlus 0.9.17.0 with errors:

lut 03 16:23:58 valheim docker-valheim-start[159389]: Feb  3 16:23:58 supervisord: valheim-server /opt/valheim/plus/valheim_server.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /opt/valheim/plus/doorstop_libs/libdoorstop_x64.so)
lut 03 16:23:58 valheim docker-valheim-start[159389]: Feb  3 16:23:58 supervisord: valheim-server /opt/valheim/plus/valheim_server.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /opt/valheim/plus/doorstop_libs/libdoorstop_x64.so)

[nkaftantzis]

Same to me. It seems to be related with the previous Issue (#768) about the version of GLIBC in the base docker image. there is a PR open about it lets hope will be merged .

[LongerHV]

Yeah, I have tried building and running the image from PR. It did fix the GLIBC errors, but I still couldn't connect from the game to the server...

[kblaschke]

Yeah, I have tried building and running the image from PR. It did fix the GLIBC errors, but I still couldn't connect from the game to the server...

Same here, Valheim Plus or rather BepinEx isn't loaded at all. Looks like BepinEx changed a few environment variables for the doorstop library (which is the injected code that loads BepinEx and then Valheim Plus).

I've updated the container to Debian 13 Trixie (the current stable release), which introduced a few additional issues like awk no longer being able to convert hex to decimal in sprintf() to check the server port. I've changed the check slightly, using awk to extract the hexadecimal port numbers, then convert them to decimal using the $((16#value)) math builtin in bash.

Also copying some i386 libs from a 32-bit Debian image to the 64-bit image also no longer works due to the lib/lib32/lib64 changes mandated by a recent systemd update. Instead, I just added the i386 architecture in the final image and install the appropriate packages there. This may increase the image size by few MB, but works just fine.

Opened another PR #771 with my fixes. Built locally, the server starts just fine.

[OldSaltGorg]

Hey @LongerHV see my comment in Issue#758 as there seem to be two overlapping problems hitting us here. I suspect because of the Engine upgrade we see a resurgence of an old thing.

[LongerHV]

Just tested solution proposed by @kblaschke and it works like a charm. #771 Fixes both problem with GLIBC and Bepinex not loading 🔥

[Grantapher]

I can confirm this V+ version we updated our bundled bepinex to the newer one that has different requirements. I can also confirm that #771 should be compatible (linux update for newer GLIBC and correct env vars set), although I'm no expert in such things, it just matches up with guidance I've seen in the mod community.

[hilts-vaughan]

Yep, that PR worked for me. I pushed an image to a personal registry and updated my personal server w/ friends to use it. I won't share the image because nobody should be running random images from me but you can build from source if you need it and it works great with Valheim+ :)