Docker images for dedicated game servers, maintained by the team behind
LANCommander. Every image is published to Docker Hub under
lancommander/<name> and is built from its own directory in Servers/.
Every image has the same shape:
Servers/<Name>/
├── Dockerfile # build file; title/description/LANCommander labels live here
├── README.md # docs; also pushed to Docker Hub as the image description
├── compose.yml # ready-to-run example, identical to the one in README.md
├── server.json # Docker Hub image name (and optional extra tag suffixes)
├── Documentation/ # longer docs, published to the LANCommander docs site
├── Hooks/<HookPoint>/NN-Name.ps1 # PowerShell hooks copied into the image
└── Scripts/ ... # launchers and other files the Dockerfile COPYs
<Name> is PascalCase (CounterStrikeSource, HalfLife2Deathmatch). It's the prefix of the
image's release tags and of its server:<Name> issue label. The image name is in server.json
and doesn't always match the directory (Battlefield1942 → lancommander/bf1942).
server.json:
{
"image": "lancommander/counterstrikesource"
}| Key | Meaning |
|---|---|
image |
Docker Hub repository. Required. |
base |
true for base layers other images build on (Base, SteamCMD, WINE). |
tagSuffixes |
Extra tag variants. WINE uses ["", "-gui"] to keep pushing its old -gui aliases. |
The base images form a chain: Base → SteamCMD → HalfLife → NaturalSelection, and
Base → WINE. Game images build FROM lancommander/<base>:latest, so a base change reaches
them when they're next built; it doesn't rebuild them.
One workflow (.github/workflows/build.yml) handles every image.
| Event | What happens |
|---|---|
Pull request, push to main |
Builds only the images whose directories changed. Nothing is pushed. Changes to only README.md, compose.yml or Documentation/ don't rebuild. |
README change on main |
Pushes that image's README to Docker Hub as its description. |
Tag <Name>/v<version> |
Builds Servers/<Name>, pushes lancommander/<image>:<version> and :latest, and updates the Docker Hub description from its README. |
| Manual run (Actions → Build images) | Builds the listed images (or all) with a chosen version; pushes unless told not to. |
To release Counter-Strike: Source 1.0.1:
git tag CounterStrikeSource/v1.0.1
git push origin CounterStrikeSource/v1.0.1The workflow needs the repository secrets DOCKERHUB_USERNAME and DOCKERHUB_TOKEN (a token
with read/write/delete access, which updating the Docker Hub description requires), and
DOCUMENTATION_DISPATCH_TOKEN for the docs site.
docker build -t lancommander/counterstrikesource:local Servers/CounterStrikeSource
# against a locally built base image
docker build -t lancommander/steamcmd:local Servers/SteamCMD
docker build --build-arg BASE_IMAGE=lancommander/steamcmd:local \
-t lancommander/counterstrikesource:local Servers/CounterStrikeSource- Copy the closest existing server directory to
Servers/<Name>/and rename everything in it. - Set
imageinserver.json, and the title/description labels in the Dockerfile. - Keep the compose example in
README.mdandcompose.ymlidentical. - Run
python3 scripts/servers.py generateto add it to the issue form and the lists below, thenpython3 scripts/servers.py check. CI runs the same check.
Use the Server problem form and pick the server; the issue is labelled server:<Name> for
triage. Requests for new games use the New server request form.
| Base image | Image | Directory |
|---|---|---|
| LANCommander Game Server Base | lancommander/base |
Servers/Base |
| Generic SteamCMD Game Server | lancommander/steamcmd |
Servers/SteamCMD |
| Generic WINE Runtime Image | lancommander/wine |
Servers/WINE |
MIT. See LICENSE.