Dockerfile for running a Killing Floor 2 server

• GitHub: https://github.com/dwurf/docker-kf2
• Docker Hub: https://hub.docker.com/r/dwurf/docker-kf2/

2GB RAM and 20GB free disk space are essential. SSD recommended, otherwise map changes will take a long time. Disk space requirements will keep going up as updates are released.

A couple of amendments specific to RHEL and any offshoots:

To allow an IPv4 address to be shared with containers on a RHEL host, you need to ensure that net.ipv4.ip_forward is enabled. This can be set using sysctl -w net.ipv4.ip_forward=1. Afterwards, you must restart docker systemctl restart docker or service docker restart depending on if you are using init.d or systemd.

With docker -v mounts you can add :z to the end of the mount argument to add the relevant SELinux contexts to use the bind mount automatically. For example -v $HOME/kf2:/home/steam/kf2server becomes -v $HOME/kf2:/home/steam/kf2server:z.

mkdir -p $HOME/{kf2,kf2_steamdir}
docker run -d -t --name kf2 -p 0.0.0.0:20560:20560/udp \
    -p 0.0.0.0:27015:27015/udp \
    -p 0.0.0.0:7777:7777/udp \
    -p 0.0.0.0:8080:8080 \
    -v $HOME/kf2:/home/steam/kf2server \
    -v $HOME/kf2_steamdir:/home/steam/steam \
    dwurf/docker-kf2:latest

Initial server state configuration is done via environment variables. To run a long game on the hard setting, run the following:

docker run -d -t --name kf2 -p 0.0.0.0:20560:20560/udp \
    -p 0.0.0.0:27015:27015/udp \
    -p 0.0.0.0:7777:7777/udp \
    -p 0.0.0.0:8080:8080 \
    -v $HOME/kf2:/home/steam/kf2server \
    -v $HOME/kf2_steamdir:/home/steam/steam \
    -e KF_DIFFICULTY=1 \
    -e KF_GAME_LENGTH=2 \
    dwurf/docker-kf2:latest

Run the container with the command update

docker run -d -t --name kf2 -p 0.0.0.0:20560:20560/udp \
    -p 0.0.0.0:27015:27015/udp \
    -p 0.0.0.0:7777:7777/udp \
    -p 0.0.0.0:8080:8080 \
    -v $HOME/kf2:/home/steam/kf2server \
    -v $HOME/kf2_steamdir:/home/steam/steam \
    dwurf/docker-kf2:latest \
    update

Further arguments get passed to the update command, e.g.

docker run -d -t --name kf2 -p 0.0.0.0:20560:20560/udp \
    -p 0.0.0.0:27015:27015/udp \
    -p 0.0.0.0:7777:7777/udp \
    -p 0.0.0.0:8080:8080 \
    -v $HOME/kf2:/home/steam/kf2server \
    -v $HOME/kf2_steamdir:/home/steam/steam \
    dwurf/docker-kf2:latest \
    update -beta preview validate

NOTE: Special characters are anything that sed considers special, so /, ^, , * etc. To escape the character, prepend \ before it as in the examples provided in the compose files and above.

1. Ensure 'command' in docker-compose.yml is not present. Updates will be handled from the first server only.
2. Expose different ports (e.g. increment) in each case, set KF_PORT, KF_QUERY_PORT (can be left as normal if it's KF_PORT + 19238) and KF_WEBADMIN_PORT (if KF_ENABLE_WEB is true) environment variables to match.
3. Change server name (optional)

Update the volume mounts as follows:

Map the following read-only volume from server 1

• $HOME/kf2:/home/steam/kf2server:ro \

Map the following read-write volumes

• $HOME/kf2-server2/steam/:/home/steam/steam
• $HOME/kf2-server2/kf2server/KFGame/Logs:/home/steam/kf2server/KFGame/Logs
• $HOME/kf2-server2/kf2server/KFGame/Config:/home/steam/kf2server/KFGame/Config

These are only required for Steam Workshop maps (see below)

• $HOME/kf2-server2/kf2server/Binaries/Win64/steamapps:/home/steam/kf2server/Binaries/Win64/steamapps
• $HOME/kf2-server2/kf2server/KFGame/Cache:/home/steam/kf2server/KFGame/Cache

You must also copy the basic config files from server1

mkdir -p $HOME/kf2-server2/kf2server/KFGame/Config
cp -a $HOME/kf2/kf2server/KFGame/Config/* $HOME/kf2-server2/kf2server/KFGame/Config

The configurator functions can be used to regenerate the KF2 configuration files. This is done using a ~/game.yml file. If this exists, ~/configurator/GenerateConfig.rb is run which templates the configuration files KFGame and KFEngine. The intention here is to allow for the map lists to more easily include customized maps.

Find the map you wish to use on the Steam workshop, for example [https://steamcommunity.com/sharedfiles/filedetails/?id=1551913612][]. Note the ID argument from the URL (1551913612) and the name of the map (KF-NachtDerUntoten_TraderPod) and add this to ~/game.yml:

custommaps:
  - name: "KF-NachtDerUntoten_TraderPod",
    steamworksids:
      - 1551913612

At runtime, the configuration files will be written and will include the map alongside the default maps (found in configurator/DefaultMaps.yml). A number of properties are possible to set for each map added via game.yml. These are listed below:

docker build -t dwurf/docker-kf2:latest .

• KF1 server in Docker

• Add support for running multiple KF2 servers from the one directory
• Map logs and config to another volume(s)
• This is docker, we shouldn't need logs (use docker logs) and config should be done via env variables (i.e. move the config file outside of the volume but it doesn't need to be exposed)
• See also ConfigSubDir under https://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(Killing_Floor_2)#Command_Line_Launch_Options
• Add support for custom map cycles https://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(Killing_Floor_2)#Maps