Closed henaff closed 10 months ago
I found a valve precision about this issue. It's not from your docker files sorry.
No worries. You are not the first person reporting this. Especially when experiencing different problems this error can be confusing.
For future reference; where did you find the Valve issue?
The given workaround was:
ln -s /home/your_user/.local/share/Steam/steamcmd/linux64/steamclient.so /home/your_user/.steam/sdk64/
ln -s /home/your_user/.local/share/Steam/steamcmd/linux32/steamclient.so /home/your_user/.steam/sdk32/
For me, it was:
mkdir /home/your_user/.steam/sdk64/
mkdir /home/your_user/.steam/sdk32/
ln -s /home/your_user/.steam/steamcmd/linux64/steamclient.so /home/your_user/.steam/sdk64/
ln -s /home/your_user/.steam/steamcmd/linux32/steamclient.so /home/your_user/.steam/sdk32/
https://developer.valvesoftware.com/wiki/Counter-Strike_2/Dedicated_Servers
Thanks for the info. I am re-opening this issue because even though it does not directly seem to be causing issues, it would be nice to include this in the Docker builds as well.
This fix has now been included in all the linux images. See commit: https://github.com/steamcmd/docker/commit/7f8456a3ce53264ed42cf93d24090811c98909bc.
Problem:
When running the Docker container for
steamcmd/steamcmd:latest
, I'm encountering an issue related to a missing shared object filesteamservice.so
.Steps to Reproduce:
steamcmd/steamcmd:latest
image:docker pull steamcmd/steamcmd:latest
/bin/sh
:docker run --entrypoint /bin/sh -it steamcmd/steamcmd:latest
steamcmd
.Expected Behavior:
I expect
steamcmd
to launch successfully without any errors.Actual Behavior:
Received the following error message:
Environment:
steamcmd/steamcmd:latest
Logs:
Additional Context:
/root/Steam/logs/stderr.txt is empty