Problem with using box86 in docker container.

[Morritz]

0007|SIGSEGV @0x6d3eb524 (???(0x6d3eb524)) (x86pc=0x6d6c6d93//hlds/cstrike/dlls/cs.so:"/hlds/cstrike/dlls/cs.so/_Z14ServerActivateP7edict_sii + 234", esp=0x763cb0c0, stack=0x75bdc000:0x763dc000 own=(nil) fp=(nil)), for accessing (nil) (code=1/prot=0), db=0x64dc57e8(0x6d3eb4b8:0x6d3eb55c/0x6d6c6d7a:0x6d6c6d9b//hlds/cstrike/dlls/cs.so/_Z14ServerActivateP7edict_sii + 234:clean, hash:3c1c1c64/3c1c1c64)
0007|Double SIGSEGV (code=1, pc=0x6d3eb524, addr=(nil))!
Missing shutdown function for Sys_InitAuthentication() : Sys_ShutdownAuthentication()
Missing shutdown function for Host_Init( &host_parms ) : Host_Shutdown()
Missing shutdown function for Sys_InitLauncherInterface() : Sys_ShutdownLauncherInterface()
Missing shutdown function for Sys_InitMemory() : Sys_ShutdownMemory()
Missing shutdown function for Sys_Init() : Sys_Shutdown()
Missing shutdown function for FileSystem_Init(basedir, (void *)filesystemFactory) : FileSystem_Shutdown()
Missing shutdown function for Sys_InitArgv( m_OrigCmd ) : Sys_ShutdownArgv()

The binary crashes with such output. It works normally outside of the docker, the base image is debian:buster-slim and binary is run using box86 binary built from git repository.

[anujdatar]

I have not used box86 inside a docker container for Counter Strike. I have only tested my docker image with TeamSpeak. But I have worked with x86 dockers of Counter Strike 1.6. I could use some more information about your docker environment, i.e. what packages did you install, dependencies, etc.

Would you be able to paste your dockerfile, or point us to your project's git repo?

[ptitSeb]

Is the segfault still happening or can the ticket be closed?

[anujdatar]

I haven't looked into this since last year, but at the time, you could run Counter Strike 1.6 on a Raspberry Pi 4 using box86-docker, as long as you installed box86 on the base OS as well.

Which was odd, because I was able to run teamspeak inside the box86-docker without having box86 installed on the base system.

I could maybe try to update my docker image and spin up a few tests over the weekend to see if anything has changed.