Skip to main content

Left 4 Dead Docker Container

This Docker container provides a fully configured Left 4 Dead game server that automatically downloads and updates the game via SteamCMD, supports file overlaying using OverlayFS, and includes optional SourceMod/MetaMod support.

Quick Start​

services:
left4dead-cooperative:
image: lancommander/left4dead:latest
container_name: left4dead-cooperative

ports:
- 27016:27015/udp
- 27021:27020/udp
- 27080:80 # For FastDL support

volumes:
- "/data/Servers/Left 4 Dead:/config"

environment:
STEAM_APP_UPDATE: "true"
START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0"
INSTALL_SOURCEMOD: "true"

cap_add:
- SYS_ADMIN

security_opt:
- apparmor:unconfined

restart: unless-stopped

Configuration Options​

Ports​

The container exposes the following ports:

  • 27015/udp - Main game server port (default). Clients connect to this port to join the server.
  • 27015/tcp - RCON (remote console).
  • 27020/udp - SourceTV port (optional). Used for game broadcasting and recording.
  • 80/tcp - HTTP file server port (optional). Used for serving game files to clients (See FastDL).

Port Mapping: In the example configuration, ports are mapped as:

  • 27016:27015/udp - Maps host port 27016 to container port 27015
  • 27021:27020/udp - Maps host port 27021 to container port 27020
  • 27080:80 - Maps host port 27080 to container port 80

You can customize these mappings based on your network requirements. If you're running multiple servers, use different host ports for each instance.

Volumes​

The container requires a volume mount for the /config directory, which stores:

  • Server/ - Game files downloaded by SteamCMD (auto-created)
  • Overlay/ - Custom files that overlay on top of the game directory
  • Merged/ - OverlayFS merged view (auto-created)
  • Scripts/ - Custom PowerShell scripts for hooks

Example:

volumes:
- "/data/Servers/Left 4 Dead:/config"

The host path can be:

  • An absolute path (Windows: C:\data\..., Linux: /data/...)
  • A relative path (e.g., ./config:/config)
  • A named volume (e.g., l4d-server-data:/config)

Important: The mounted directory must be writable by the container.

Environment Variables​

VariableDescriptionDefaultRequired
STEAM_APP_IDSteam app id of the dedicated server222840No
STEAM_APP_UPDATEEnable automatic game updates on startup (true/false)trueNo
START_EXEServer executable (relative to the game directory)srcds_runNo
START_ARGSArguments used to start the game server"-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0"No
GAME_MODGame directory that SourceMod/MetaMod are installed intoleft4deadNo
INSTALL_SOURCEMODEnable SourceMod/MetaMod installation (true/false)trueNo
SOURCEMOD_MAJOR_VERSIONSourceMod release branch1.12No
SOURCEMOD_VERSIONSourceMod version to install1.12.0-git7221No
SOURCEMOD_URLOverride the SourceMod download URL(unset)No
METAMOD_MAJOR_VERSIONMetaMod:Source release branch1.12No
METAMOD_VERSIONMetaMod version to install1.12.0-git1219No
METAMOD_URLOverride the MetaMod download URL(unset)No
HTTP_FILESERVER_ENABLEDServe custom content over HTTP (FastDL) on port 80trueNo
HTTP_FILESERVER_WEB_ROOTDirectory served by the HTTP file server/config/Merged/left4deadNo
HTTP_FILESERVER_FILE_PATTERNRegex of request paths the file server allowsmaps, materials, models and sound filesNo

STEAM_APP_UPDATE​

Controls whether SteamCMD updates the game server on container startup.

  • "true" - Automatically download/update the game server
  • "false" - Skip updates (useful for offline operation or faster startup)

Example:

environment:
STEAM_APP_UPDATE: "true"

START_ARGS​

Arguments passed to the game server executable at startup.

Default:

START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0"

Customization Examples:

Basic server with custom map:

START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0"

Internet server bound to all interfaces:

START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0 +sv_lan 0 +ip 0.0.0.0"

Server with RCON password:

START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0 +rcon_password mypassword"

Common Server Parameters:

  • +map <mapname> - Set the starting map (e.g., l4d_hospital01_apartment, l4d_airport01_greenhouse)
  • +mp_gamemode <mode> - coop (default, 4 players) or versus (8 players); versus needs a l4d_vs_* map
  • +sv_allow_lobby_connect_only 0 - Allow players to join with connect <ip> instead of through a Steam lobby (set by default)
  • +sv_lan 0 - Enable internet play (0 = internet, 1 = LAN only)
  • +ip <address> - Server IP address (use 0.0.0.0 for all interfaces)
  • +port <port> - Server port (default: 27015)
  • +rcon_password <password> - RCON password for remote administration
  • +hostname "<name>" - Server name displayed in server browser

INSTALL_SOURCEMOD​

Enables automatic installation of SourceMod and MetaMod:Source, which provide plugin support and enhanced server administration.

  • "true" - Install SourceMod and MetaMod
  • "false" - Skip SourceMod installation

Default: "true".

When enabled, the container will:

  1. Download and install MetaMod:Source (required dependency)
  2. Download and install SourceMod
  3. Place all files in /config/Overlay/left4dead/addons/

Example:

environment:
INSTALL_SOURCEMOD: "true"

Security Options​

The container requires elevated privileges to use OverlayFS for file overlaying.

cap_add: SYS_ADMIN​

Adds the SYS_ADMIN capability, which is required for mounting OverlayFS. This is the recommended approach as it provides minimal necessary privileges.

cap_add:
- SYS_ADMIN

security_opt: apparmor:unconfined​

On Ubuntu hosts with AppArmor enabled, you may need to disable AppArmor restrictions for the container. This is often necessary for OverlayFS to function properly.

security_opt:
- apparmor:unconfined

Alternative Options:

If you prefer less security but simpler configuration, you can use privileged mode:

privileged: true

Note: Privileged mode grants the container extensive access to the host system and is less secure than using cap_add: SYS_ADMIN.

Restart Policy​

restart: unless-stopped

This ensures the container automatically restarts if it stops unexpectedly, but won't restart if you manually stop it.

Other options:

  • no - Never restart
  • always - Always restart, even after manual stop
  • on-failure - Restart only on failure

Directory Structure​

The /config directory contains the following structure:

/config/
├── Server/ # Game files from SteamCMD (auto-created)
│ └── left4dead/ # Left 4 Dead game directory
├── Overlay/ # Custom files overlay (your modifications)
│ └── left4dead/
│ ├── addons/ # SourceMod/MetaMod installation location
│ │ ├── sourcemod/
│ │ │ ├── plugins/ # Place .smx plugin files here
│ │ │ ├── configs/ # SourceMod configuration files
│ │ │ └── ...
│ │ └── metamod/
│ ├── maps/ # Custom maps
│ ├── cfg/ # Server configuration files (server.cfg, etc.)
│ └── ...
├── Merged/ # OverlayFS merged view (auto-created)
├── .overlay-work/ # OverlayFS work directory (auto-created)
└── Scripts/
└── Hooks/ # Custom PowerShell scripts for hooks

SourceMod Configuration​

Installing Plugins​

Once SourceMod is installed, add plugins by placing compiled .smx files in:

/config/Overlay/left4dead/addons/sourcemod/plugins/

Example:

# Copy plugin to the overlay directory
cp my_plugin.smx "/data/Servers/Left 4 Dead/Cooperative/Overlay/left4dead/addons/sourcemod/plugins/"

# Restart the container to load the plugin
docker restart left4dead-cooperative

SourceMod Configuration Files​

Place SourceMod configuration files in:

/config/Overlay/left4dead/addons/sourcemod/configs/

Common configuration files:

  • admins_simple.ini - Admin user configuration
  • core.cfg - Core SourceMod settings
  • database.cfg - Database configuration (if using database features)

Server Configuration​

Place server configuration files in:

/config/Overlay/left4dead/cfg/

Example server.cfg:

hostname "My Left 4 Dead Server"
sv_lan 0
sv_allow_lobby_connect_only 0
rcon_password "your_rcon_password"

Match Statistics​

The server can report the matches played on it to LANCommander, with the LANCommander match statistics plugin. The plugin is built into the image and needs SourceMod (INSTALL_SOURCEMOD). It is turned on when MATCH_STATS_SERVER_URL and MATCH_STATS_TOKEN are set, and is then copied into left4dead/addons/sourcemod/ on every start. The core plugin loads the Left 4 Dead module itself. Turned off, the plugin's files are removed again.

VariableDescriptionDefault
MATCH_STATS_ENABLEDauto: on when MATCH_STATS_SERVER_URL and MATCH_STATS_TOKEN are set. true or falseauto
MATCH_STATS_SERVER_URLThe LANCommander server, e.g. http://lancommander.lan:1337. Only http:// works on Linux(empty)
MATCH_STATS_TOKENA LANCommander access token with the Report matches scope (Profile → Access Tokens). It isn't written to any file(empty)
MATCH_STATS_GAME_IDThe game's id in LANCommander(empty)
MATCH_STATS_SERVER_IDThis server's id in LANCommander, if LANCommander manages it(empty)
MATCH_STATS_REPORTER_NAMEHow the server is named in LANCommander(hostname)
MATCH_STATS_MIN_PLAYERSHuman players needed before a match is recorded(1)
MATCH_STATS_MODEThe mode reported. Empty lets the game module decide(empty)
MATCH_STATS_RECORD_BOTSRecord bots as players (true/false)(true)
MATCH_STATS_RECORD_CHATRecord chat messages (true/false)(false)
MATCH_STATS_ATTACH_DEMOSUpload SourceTV demos recorded with tv_record (true/false)(true)

The settings are written to left4dead/cfg/sourcemod/lancommander.cfg as lc_* cvars on every start. Settings left empty aren't written, so they and the plugin's other lc_* cvars (see its README) can be set in left4dead/cfg/sourcemod/sourcemod.cfg instead. A lancommander.cfg you put in Overlay/left4dead/cfg/sourcemod/ yourself is left alone.

sm_lc_status on the server console or over RCON shows the match being recorded and how delivery is going. Reports that couldn't be delivered yet are kept in Overlay/left4dead/addons/sourcemod/extensions/.interposer/Matches/ and sent once LANCommander can be reached.

OverlayFS​

The container uses Linux OverlayFS to merge the base game files with your custom files:

  • Lower layer: /config/Server (base game files from SteamCMD)
  • Upper layer: /config/Overlay (your custom files)
  • Merged view: /config/Merged (where the game server runs from)

Benefits:

  • Replace files without modifying the base installation
  • Add custom content (maps, plugins, configs)
  • No file copying required - OverlayFS is a union filesystem
  • Easy updates - base game files can be updated without losing customizations

If OverlayFS cannot be mounted (e.g., missing privileges), the container will fall back to using /config/Server directly and log a warning.

Troubleshooting​

Container Won't Start​

  1. Check logs:

    docker logs left4dead-cooperative
  2. Verify permissions: Ensure the mounted volume is writable:

    # Linux
    chmod -R 755 "/data/Servers/Left 4 Dead/Cooperative"

    # Windows
    # Ensure the directory has proper permissions in Windows
  3. Check security options: Ensure cap_add: SYS_ADMIN is set, or use privileged: true

Game Server Not Starting​

  1. Verify START_ARGS: Check that START_ARGS contains valid server arguments:

    START_ARGS: "-game left4dead -console +map l4d_hospital01_apartment +sv_allow_lobby_connect_only 0"
  2. Check server directory: Verify that game files were downloaded:

    docker exec left4dead-cooperative ls -la /config/Server/left4dead
  3. Review server logs: Check container logs for server startup messages and errors

SourceMod Not Loading​

  1. Verify installation: Ensure INSTALL_SOURCEMOD: "true" is set (with quotes in YAML)

  2. Check installation directory:

    docker exec left4dead-cooperative ls -la /config/Overlay/left4dead/addons/sourcemod
  3. Verify MetaMod: Check that MetaMod is installed:

    docker exec left4dead-cooperative ls -la /config/Overlay/left4dead/addons/metamod.vdf
  4. Check server console: Look for SourceMod loading messages in the container logs

OverlayFS Warnings​

If you see warnings about OverlayFS:

  1. Verify capabilities: Ensure cap_add: SYS_ADMIN is present in your docker-compose.yml

  2. Check AppArmor: On Ubuntu, add security_opt: apparmor:unconfined

  3. Alternative: Use privileged: true (less secure but simpler)

ERROR! Failed to install app '222840' (Missing configuration)​

The Left 4 Dead Dedicated Server app only defines a Windows launch configuration on Steam, so a fresh Linux install fails with this error. The image handles this in the PreSteamInstallGame/10-BootstrapInstall.ps1 hook: when Server/steamapps/appmanifest_222840.acf doesn't exist yet, it installs once with the Windows platform, and the normal Linux install then adds the Linux binaries. Later updates work as usual. If the first install was interrupted, delete Server/steamapps/appmanifest_222840.acf and restart the container to run the bootstrap again.

Players can't join with connect <ip>​

Left 4 Dead servers only accept players coming from a Steam matchmaking lobby unless sv_allow_lobby_connect_only is 0. The default START_ARGS sets it; if you override START_ARGS or set it in server.cfg, keep it at 0. For a LAN-only server also add +sv_lan 1.

Versus mode loads the wrong map or kicks players​

Versus uses its own map set (l4d_vs_hospital01_apartment, l4d_vs_airport01_greenhouse, ...). Set +mp_gamemode versus together with a l4d_vs_* map; campaign maps (l4d_hospital01_apartment) are for coop.

Failed to open bin/dedicated_srv.so on first boot​

On the very first start the overlay is mounted before SteamCMD has created Server/bin, so srcds_run can't find the engine. The automatic restart (restart: unless-stopped) picks it up on the next start; no action is needed.

Port Already in Use​

If you get port binding errors:

  1. Check for existing containers:

    docker ps -a
  2. Use different ports: Change the port mapping in docker-compose.yml:

    ports:
    - 27017:27015/udp # Use a different host port
  3. Stop conflicting containers:

    docker stop <container-name>

Permission Errors​

The container runs as a non-root user. If you encounter permission errors:

  1. Check file ownership:

    docker exec left4dead-cooperative ls -la /config
  2. Verify volume mount: Ensure the host directory is accessible and writable

  3. Review logs: Check container logs for specific permission error messages

Advanced Usage​

Custom Hooks​

You can create custom PowerShell scripts that execute at various points in the container's lifecycle. Place scripts in:

/config/Scripts/Hooks/{HookName}/

Available hooks:

  • PreSteamInstallGame - Before SteamCMD runs
  • PostSteamInstallGame - After SteamCMD completes
  • PreInstallSourceMod - Before SourceMod installation
  • PostInstallSourceMod - After SourceMod installation

Example hook script (/config/Scripts/Hooks/PostSteamInstallGame/10-CustomSetup.ps1):

Write-Host "Running custom setup..."
# Your custom commands here

HTTP File Server​

The container includes an optional HTTP file server (port 80) for serving game files to clients. This is useful for fast downloads of custom maps and content.

The file server is configured via environment variables:

  • HTTP_FILESERVER_ENABLED - Enable/disable the file server
  • HTTP_FILESERVER_WEB_ROOT - Root directory for file serving
  • HTTP_FILESERVER_FILE_PATTERN - Pattern for files to serve

Multiple Server Instances​

To run multiple Left 4 Dead servers on the same host:

  1. Use different container names:

    container_name: left4dead-server1
  2. Use different ports:

    ports:
    - 27016:27015/udp
    - 27021:27020/udp
  3. Use different volume mounts:

    volumes:
    - "/data/Servers/Left 4 Dead/Server1:/config"
  4. Use different maps/names:

    environment:
    START_ARGS: "-game left4dead -console +map l4d_airport01_greenhouse +sv_allow_lobby_connect_only 0 +hostname 'Server 1'"

Additional Resources​