A docker image for SteamCMD
docker run -it pavolab/steamcmdor in Dockerfile and docker-compose
FORM: pavolab/steamcmd
Which ports do I need to open for Steam?
| To log into Steam and download content |
|---|
| HTTP (TCP port 80) and HTTPS (443) |
| UDP 27015 through 27030 |
| TCP 27015 through 27030 |
| Steam Client |
|---|
| UDP 27000 to 27015 inclusive (Game client traffic) |
| UDP 27015 to 27030 inclusive (Typically Matchmaking and HLTV) |
| UDP 27031 and 27036 (incoming, for In-Home Streaming) |
| TCP 27036 and 27037 (incoming, for In-Home Streaming) |
| UDP 4380 |
| Dedicated or Listen Servers |
|---|
| TCP 27015 (SRCDS Rcon port) |
| Streamworks P2P Networking and Steam Voice Chat |
|---|
| UDP 3478 (Outbound) |
| UDP 4379 (Outbound) |
| UDP 4380 (Outbound) |
Steam (http://www.steampowered.com) is a software content delivery system developed by Valve software (http://www.valvesoftware.com). There is some free software available, but for the most part the content delivered is non-free.
The Steam Console Client or SteamCMD is a command-line version of the Steam client. Its primary use is to install and update various dedicated servers available on Steam using a command-line interface.
This package comes with a fairly substantial non-free license agreement that must be accepted before installing the software.