Warfork server on Docker!
$ docker run \
-v=wf:/home/warfork/server \
-v=/path/to/wflogs:/home/warfork/.local/share/warfork-2.1/basewf \
--net=host \
gelmo/warfork-docker
- The server will be installed on a named volume
wfto persist the server files. - The server's logs and demos directory will be mapped to the
/path/to/wflogsdirectory to persist the logs and demos. - The server will be running on the
hostnetwork for optimal network performance
Default: /var/wf
Absolute path to a directory in the container containing custom config and map files. Changing this is not recommended in order to follow the documentation.
Additional parameters to pass to wf_server.x86_64 (for example, +sv_hostname "Insta Server" +g_instagib "1").
The server can be populated with your own config files and maps by copying the files from the custom configs directory located at WF_CUSTOM_CONFIGS_DIR to the basewf folder at each start of the container. WF_CUSTOM_CONFIGS_DIR is a mounted directory from the host system. The custom configs directory must have same folder structure as the basewf folder in order to add or overwrite the files at the paths.
Add configs and maps to /home/user/wf:
.
├── progs
│ └── gametypes
│ └── configs
│ ├── wipeout.as # Will be added
│ ├── wipeout.gt # Will be added
│ └── wipeout.gtd # Will be added
├── dedicated_autoexec.cfg # Will be overwritten
└── map_claustrophobia.pk3 # Will be added
Mount /home/user/wf to WF_CUSTOM_CONFIGS_DIR in the container:
$ docker run \
-v=wf:/home/warfork/server \
-v=/path/to/wflogs:/home/warfork/.local/share/warfork-2.1/basewf \
-v=/home/user/wf:/var/wf \ # Mount the custom configs directory
--net=host \
gelmo/warfork-docker
Default: false
Validate and restore missing/broken server files on container start. Can be enabled with true.
Default: false
Print all executed commands for better debugging.
Once the server has been installed, the container will check for an update at every start.
Restart the container with docker restart.
Container named wf:
$ docker restart wf