protonscr

Docker no longer allows SteamCMD network access pattern

steamclosed SteamCMD
ValveSoftware/steam-for-linux#13149 · opened 2026-05-03 by JustinTArthur · updated 2026-05-08 · 10 comments · github
JJustinTArthur 2026-05-03 github

Your system information

  • SteamCMD
  • Docker 29.4.2 on any modern Linux distribution

Please describe your issue in as much detail as possible:

With SteamCMD still being 32-bit and closed-source, it's paired with a compatible 32-bit glibc. 32-bit glibc in turn uses the Linux kernel's old socketcall system call for socket operations.

As socketcall has been cited for its potential to work around security restrictions, it's starting to be blocked or constrained in some of the most common security policies, including Docker's own default seccomp policy as of moby/profiles#21

Example SteamCMD output when it's been restricted:

CreateBoundSocket: failed to create socket, error [no name available] (38)
Retrying... 
CreateBoundSocket: failed to create socket, error [no name available] (38)
Retrying... 
CreateBoundSocket: failed to create socket, error [no name available] (38)
FAILED (No Connection)
Unloading Steam API...
OK

Downstream bug reports:

  • community-valheim-tools/valheim-server-docker#780
  • indifferentbroccoli/windrose-server-docker#54
  • pelican-eggs/games-steamcmd#277
  • pterodactyl/game-eggs#540

Steps for reproducing this issue:

  1. Attempt to use SteamCMD for Linux to install or update a game on the most recent Docker version
GGeeekie 2026-05-03 github

Can confirm that this is a problem that needs attention from Valve.

Ccrywolfy 2026-05-04 github

At the moment only fix for me was downgrading to Docker-CE 29.4.1 (according to https://github.com/moby/moby/issues/52506#issuecomment-4362704302) , but yes staying with outdated packages doesn't seem a stable solution, is this a SteamCMD problem or mabye a Docker one ?

GGeeekie 2026-05-04 github

At the moment only fix for me was downgrading to Docker-CE 29.4.1 (according to moby/moby#52506 (comment)) , but yes staying with outdated packages doesn't seem a stable solution, is this a SteamCMD problem or mabye a Docker one ?

I tried this: https://github.com/community-valheim-tools/valheim-server-docker/issues/780 and it then worked for me without having to downgrade, but yes its not optimal.

44budab1 2026-05-04 github

Yep, same issue,
but im using noob friendly setup panel and can't change files to add
workaround fix like this https://github.com/community-valheim-tools/valheim-server-docker/issues/780
Add seccomp=unconfined to your docker-compose.yml

Ccrywolfy 2026-05-04 github

Yep, same issue, but im using noob friendly setup panel and can't change files to add workaround fix like this community-valheim-tools/valheim-server-docker#780 Add seccomp=unconfined to your docker-compose.yml

That's nice but this cannot be done in Pterodactyl or im mistaking ?

Llostgoat 2026-05-05 github

Thanks for the issue report @JustinTArthur

We took a look at this yesterday and it seems like the seccomp change on the docker side had a larger impact than the change author expected. For more details, I left a comment on the moby issue tracker here:
https://github.com/moby/moby/issues/52506#issuecomment-4376715313

Docker has an official workaround here:
https://docs.docker.com/engine/release-notes/29/#known-issues

It looks like they will be releasing a proper fix for the issue tomorrow.

JJustinTArthur 2026-05-06 github

Thanks for the issue report @JustinTArthur

We took a look at this yesterday and it seems like the seccomp change on the docker side had a larger impact than the change author expected. For more details, I left a comment on the moby issue tracker here: moby/moby#52506 (comment)

Docker has an official workaround here: https://docs.docker.com/engine/release-notes/29/#known-issues

It looks like they will be releasing a proper fix for the issue tomorrow.

Thank you, @lostgoat, for providing the Moby project (and us) with a detailed investigation, including that rundown on the major distros. I think your research directly helped drive the reconsideration of the blanket block and the decision to pause backports and sideports.

I've adjusted the PR title and description as the containerd port for the change has also been reconsidered. The Containers project has not moved to block socketcall in podman or crun. With that in mind, feel free to close this out after the Docker release, but I'll reverberate the interest in an x86_64 SteamCMD.

Rreal-rayman 2026-05-06 github

A new docker release is out (https://github.com/moby/moby/releases/tag/docker-v29.4.3). Upgrading docker to 29.4.3 fixes the issue.

Ddavid-rawnsley 2026-05-08 · hidden on GitHub github

Now getting the following error after updating to the latest version (downgrading to the previous working version still works). Is this a new issue or still the same one but manifesting differently?

ERROR: HTTP 429 for https://umod.org/extensions/discord/download it is a valid link

Llostgoat 2026-05-08 github

@real-rayman Thanks for confirming the update fixes it on your side.

@david-rawnsley That seems like something unrelated. The steamcmd binary has no references to that link, and I'm assuming docker doesn't either. You probably want to chat with whatever layer you are using above these two tools.

Nothing extracted yet.