|Daniel Lawrence a0205f5263 force executable||3 years ago|
|Dockerfile||3 years ago|
|README.md||3 years ago|
|tf.sh||5 years ago|
|tf2_ds.txt||5 years ago|
|update.sh||5 years ago|
By default image is build with enabled autoupdate feature (take a look at
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
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.