protonscr

steamcmd not working properly in Ubuntu Focal container

steamopen SteamCMDDistro Family: Ubuntu
ValveSoftware/steam-for-linux#7190 · opened 2020-06-12 by DerEnderKeks · updated 2021-05-15 · 6 comments · github
DDerEnderKeks 2020-06-12 github

Your system information

  • Steam client version (build number or date): -
  • Distribution: Ubuntu (Focal) in Docker (Host OS is CentOS 7)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

When trying to start steamcmd in an Ubuntu Focal Docker container (didn't test outside of Docker) it crashes with the following errors:

Log 
root@51a02b4f0eef:/home/steam/steamcmd# ./steamcmd.sh
Redirecting stderr to '/root/Steam/logs/stderr.txt'
threadtools.cpp (3787) : Assertion Failed: Probably deadlock or failure waiting for thread to initialize.
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
[  0%] Checking for available update...
threadtools.cpp (3787) : Assertion Failed: Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize
CWorkThreadPool::StartWorkThread: Thread creation failed.
Exiting on SPEW_ABORT

When trying with the exact same setup on Ubuntu Eoan or Debian Buster it works just fine:

Log 
root@e33fdf108d56:/home/steam/steamcmd# ./steamcmd.sh
Redirecting stderr to '/root/Steam/logs/stderr.txt'
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
[  0%] Checking for available update...
[----] Downloading update (0 of 51208 KB)...
[...]
[100%] Downloading update (51208 of 51208 KB)...
[100%] Download Complete.
[----] Applying update...
[----] Extracting package...
[...]
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching...
WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/root/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...Warning: failed to init SDL thread priority manager: SDL not found
OK.

Steam>

Steps for reproducing this issue:

  1. Install Docker
  2. Start an Ubuntu Focal container docker run --rm -it ubuntu:focal
  3. Update & install steamcmd
apt update && apt upgrade -y && apt install -y curl lib32gcc1 &&\
mkdir -p /home/steam/steamcmd && cd /home/steam/steamcmd &&\
curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar zxvf -
  1. Run ./steamcmd.sh
Ccubuzz 2020-12-13 github

Issue still occcurs, also on debian and arch.

Ssukoneck 2020-12-22 github

+1

Jjimbo8098 2021-02-19 github

I looked into a similar issue on https://github.com/dwurf/docker-kf2/ , the problem here is that the library the steamcmd refers to is not available in the focal repos for apt installs. My PR which might help explain is here https://github.com/dwurf/docker-kf2/pull/15 .

Your error log doesn't show the specific error mine referred to but I needed to install libcurl4 alongside the other packages in your apt install.

I seem to remember it was something to do with the packages it was using before no longer being supported for some reason but given that your error isn't the same, this may be a stab in the dark... Either way, I hope it helps!

Ffarvour 2021-03-12 github

2021, and Valve still can't get it together and build 64-bit software. :facepalm: When are they going to actually move on this? When Windows 10 finally yanks 64-bit support in the next version of Windows? When pretty much NOBODY has 32-bit instructionsets anymore?

This stuff is frustrating. 14+ years and zero effort towards building a 64-bit release of steamCMD. Look Valve, I understand there might not be any $$$$ in it, but it's seriously in everyone's best interest to ditch this 32-bit nonsense.

Jjimbo8098 2021-04-14 github

2021, and Valve still can't get it together and build 64-bit software. 🤦 When are they going to actually move on this? When Windows 10 finally yanks 64-bit support in the next version of Windows? When pretty much NOBODY has 32-bit instructionsets anymore?

This stuff is frustrating. 14+ years and zero effort towards building a 64-bit release of steamCMD. Look Valve, I understand there might not be any $$$$ in it, but it's seriously in everyone's best interest to ditch this 32-bit nonsense.

What makes you think this is a 32 vs 64-bit issue?

AAndrewMarchukov 2021-05-15 github

I have many steamcmd docker builds on Focal without errors: https://github.com/AndrewMarchukov/insurgency-sandstorm-server-dockerize/runs/2587921151?check_suite_focus=true
and i build on my server locally no errors too
Docker file here

Nothing extracted yet.