This Docker image will download the required ET:Legacy maps as specified in the MAPS environment variable (from REDIRECTURL) and then spawn an ET:Legacy server with latest snapshot, with configuration as defined in the environment variables or their defaults (refer below).

If you want to avoid downloading maps over HTTP(s), you can mount a volume of maps to /maps/. By default all .pk3 files found in /maps/ are automatically copied into the server — no need to list them in MAPS. Set MAPS_AUTO=false to disable auto-scanning and rely on explicit MAPS entries only.

All logs are written to STDOUT so can be viewed from docker logs or run without the -d Docker run switch.

A container using this image will always try and download the latest changes from whatever SETTINGSURL is set to. By default this is legacy-configs

• Based on msh100's rtcwpro repository with significant changes
• Tag stable is recommended for competitive play and actively maintained.
• Automatic builds triggered by ET:Legacy snapshot releases
• Available tags listed on Docker Hub
• Includes a built-in autorestart daemon that periodically checks player count and sends a restart signal when the server is empty (or below the configured threshold). Enabled by default, runs every 2 hours. Can also be invoked as a one-shot command (e.g. via Watchtower lifecycle hook).

services:
  etl-server:
    container_name: etl-server
    image: oksii/etlegacy:stable
    environment:
      - 'HOSTNAME=ET Legacy Docker' 
      - 'MAPS=adlernest:braundorf_b4:supply:sw_goldrush_te'
      - 'PASSWORD=etlserver'
    volumes:
      - ./maps:/maps
    ports:
      - '27960:27960/udp'
    stdin_open: true
    tty: true
    restart: unless-stopped

docker run -d \
  -p "27960:27960/udp" \
  -e "MAPS=adlernest:te_escape2:frostbite" \
  -e "PASSWORD=war" \
  -e "REFEREEPASSWORD=pass123" \
  oksii/etlegacy:stable

docker-install-script.sh script will install the required packages and docker, and guide you through a set of configuration options (see Configuration).

Also features the optional setup of:

• watchtower
• a minimalistic webserver for REDIRECTURL and wwwDownloads
• automatic restarts via cron to avoid performance degradation
• a helper utility that interacts with the server and docker for easy manage (etl-server)

Allows for single or multiple instances configuration.

Install script uses the docker-compose method and will output to a directory of your choice, configuration can easily be edited by modifying settings.env post-install.

cd ~ && \
    curl -sSL https://raw.githubusercontent.com/Oksii/etlegacy/main/example/docker-install-script.sh \
        -o docker-install-script.sh && \
    chmod +x docker-install-script.sh && \
    sudo ./docker-install-script.sh

Available environment variables:

Extra configuration can be prepended to the etl_server.cfg by mounting a configuration at /legacy/server/extra.cfg. This is generally not recommended, try to use the variables above where possible or create a custom SETTINGSURL.

Automatic updates and restarts, ensuring servers are only restarted when no players are present. By using watchtower's --enable-lifecycle-hooks and adding the following labels to your ET:L service. The autorestart binary runs in one-shot mode when invoked as a lifecycle hook: it exits 0 (proceed with update) only if the player count is at or below AUTORESTART_PLAYERS, otherwise exits 1 (abort).

  labels:
    - "com.centurylinklabs.watchtower.enable=true"
    - "com.centurylinklabs.watchtower.lifecycle.pre-update=/legacy/server/autorestart"

  watchtower:
    container_name: watchtower
    image: containrrr/watchtower
    command: --enable-lifecycle-hooks
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    labels:
      - "com.centurylinklabs.watchtower.enable=false"
      - "com.watchtower=watchtower"

The etl-server helper script provides a convenient way to manage your ET:Legacy server instances through simple commands. This utility is automatically installed when using the guided install script.

etl-server [start|stop|restart|status|logs|rcon|update] [instance_number] [command]

The status command displays detailed information about your servers:

• Container status and uptime
• Server name and current map
• Active players
• Port configuration
• Password settings

The update command includes safety checks:

• Checks for active players before updating
• Warns if servers have players connected
• Provides --force option for urgent updates
• Shows detailed server state before update

etl-server start            # Start all server instances
etl-server stop 2           # Stop specific instance
etl-server status           # View status of all servers
etl-server update 2         # Update specific instance (checks for players first)
etl-server update 2 --force # Force update even with active players
etl-server rcon 1 map radar # Execute RCON command on instance 1
etl-server logs 2           # View live logs for instance 2

• The script requires Docker and docker-compose to be installed
• Multiple instance support is configured during initial setup
• All commands respect the configuration in your settings.env file
• Updates check for active players by default to prevent disruption