Container crashes ui on synology docker

[exedox]

I'm running into the same issue as this person:
https://www.reddit.com/r/synology/comments/uo3and/docker_keeps_crashing_the_ui/

I'd have the container up and running, and then as soon as it starts, the ui is locked out for me. I'm not sure if the server worked itself since I didn't have the chance to look for the game ID to test.

[Micke90s]

A few more information to this case.

Based on the Reddit comments this is caused by different versions of the linux kernels. The synology uses a old (not clearly specified) kernel while the docker image is based on a Debian 11 kernel.

Unfortunately, I think this is nothing what we can fix on the main branch, as the problem is already based on the underlaying docker image cm2network/steamcmd:root.

Source:
• https://www.reddit.com/r/synology/comments/z5vkbr/comment/iy4z8n7/
• https://www.reddit.com/r/synology/comments/uo3and/docker_keeps_crashing_the_ui/
• https://www.reddit.com/r/CoreKeeperGame/comments/17akmmd/dedicated_server_for_synology/

[Micke90s]

Update:
I mixed up the Dockerfiles of cm2network/steamcmd and escaping/core-keeper-dedicated to change the Linux system to debian:buster-slim

Core Keeper seems not to be compatible with Debian 10 (Buster). As xvfb is too old:

See https://discourse.cubecoders.com/t/core-keeper-segmentation-fault/3623

A recent update to CoreKeeper means that it now requires a later version of Xvfb that is only present on later distros like Ubuntu 22.04 and Debian 12. AMP’s docker images uses Debian 11, hence you get the error.

The old xvfb causes the segmentation fault error. As a workaround I used the xvfb from Debian 11 (Bullseye). This seems to work on my machine. But I am not sure if this workaround is the best solution.

If anyone got a better idea feel free to add a comment.

Please see https://github.com/Micke90s/core-keeper-dedicated/tree/debian10

[Micke90s]

Update:
I tried to install the docker image on a virtual maschine running Synology DVA1622.
Everyting works fine till the installation of xvfb (and its dependencies) from Bullseye. This causes the system to run at 100% and freezes the complete UI.

So the problem is, that using the latest xvfb causes a system freeze while using it not causes a Segmentation fault

I don't have any more ideas at the moment

Aditional information:

• steamcmd: Terminating m_ThreadClient, likely to crash down the line ValveSoftware/steam-for-linux#8083