100% CPU Usage can't kill container about csgo

[sploittastic]

Same issue on my DS1019+ synology with a new pull of cm2network/csgo:sourcemod. It eats all CPU on the box and I have to use kill -9 on the container pid. After I kill the PID which stops the container, I see the following in the logs:

src/tier0/threadtools.cpp (4122) : Probably deadlock or failure waiting for thread to initialize.

@Watashi199 try "kill -9 ", that works for me. docker stop/kill just hang for me.

[rsalus]

This is an issue with the Synology OS using an incompatible fork of Linux.

Basically: steamcmd hangs/crashes with glibc versions >= 2.31 due to collisions in the syscall number assignments.

EX:

See here for a full explanation. There is a workaround here but it is a little wonky. @CM2Walki would this be possible to implement?

[Watashi199]

It would be cool to mention it on the docker hub/github page to avoid this kind of issue ahah