Dockerfile for a basic Team Fortress 2 server
  • Dockerfile 79.6%
  • Shell 20.4%
Find a file
Robin Appelman e66df023bc add unzip
2015-11-22 16:02:02 +01:00
Dockerfile add unzip 2015-11-22 16:02:02 +01:00
README.md s/my/use my 2015-08-07 21:55:23 +02:00
tf.sh Init 2013-11-03 14:45:11 +03:00
tf2_ds.txt Init 2013-11-03 14:45:11 +03:00
update.sh Init 2013-11-03 14:45:11 +03:00

Team Fortress 2 + Docker

Details:

By default image is build with enabled autoupdate feature (take a look at tf.sh file). You can create new Dockerfile based on that image (FROM tf2) and customize it with plugins, configs, CMD and ENTRYPOINT instructions.

# Build image and tag it as tf2
docker build -t tf2 github.com/Gonzih/docker-tf2-server

# Run image with default options (CMD in Dockerfile)
docker run -d -p 27015:27015/udp tf2

# Run image with custom options
docker run -d -p 27015:27015/udp tf2 +sv_pure 2 +map ctf_2fort.bsp +maxplayers 32

# Run image with custom config
docker run -d -p 27015:27015/udp -v ~/server.cfg:/home/tf2/hlserver/tf2/tf/cfg/server.cfg:ro tf2

Why this image is not on the public docker hub?

I personaly don't like idea of downloading binary executable blob that runs in a daemon with root permissions on my server. Docker is far from being secure (at least at the current moment). So building your own image is much better option in that sense.

Also this image is quiet heavy (~ 6.2 Gb) and with current hub speeds I don't have patience to upload it. It might be possible that downloading tf2 server from steam is faster then downloading image from docker hub.

Again I strive to use my own images (FROM scratch), so no plans on uploading this to hub right now.