No description
Find a file
Sebastian Hugentobler c8c4b775b1
Some checks failed
Vanwa Containers/etlegacy/pipeline/tag There was a failure building this commit
make it compile on aarch64
2025-09-01 12:35:52 +02:00
Containerfile make it compile on aarch64 2025-09-01 12:35:52 +02:00
Jenkinsfile setup jenkins CI 2025-09-01 10:54:37 +02:00
README.md make it compile on aarch64 2025-09-01 12:35:52 +02:00

ET: Legacy Dedicated Server

Dedicated server container for Enemy Territory: Legacy.

The original game assets are under a restrictive license and need to be provided separately. Easiest way is to download the windows installer from the original website, open it up as an archive and unpack pak0.pk3, pak1.pk3 and pak2.pk3.

Volumes

  • /etlegacy/.etlegacy/: Log files, databases and cache.
  • /etlegacy/etmain: Configuration and data files. Put the original game files and custom maps in here. Default configuration files can be found in the etlegacy repository.
  • /etlegacy/legacy/omni-bot/et/nav/: Waypoint files for omnibot.
  • /etlegacy/legacy/omni-bot/et/user/omni-bot.cfg: OmniBot configuration.

The container user has uid/guid 2222. Ensure the volumes have the proper permissions (even better, run it with id mapping).

Ports

  • 27960/udp

Example

Example invocation using podman:

podman run -it --userns=keep-id:uid=2222,gid=2222 -p 27960:27960/udp -v "$PWD/vol/etmain":/etlegacy/etmain/ -v "$PWD/vol/nav":/etlegacy/legacy/omni-bot/et/nav/ -v "$PWD/vol/data/":/etlegacy/.etlegacy/ etlegacy

This maps the host user to the container user and sets up volume mounts.