This image will always install/update to the latest steamcmd and 7 Days to Die server, all you have to do to update your server is to redeploy the container.
Also note that the entire /steamcmd/7dtd can be mounted on the host system, which would avoid having to reinstall the game when updating or recreating the container.
- First time only: Rename .env-sample to .env # This is where you'll hold information such as server & telnet password.
- Optionally set the
SEVEN_DAYS_TO_DIE_SERVER_STARTUP_ARGUMENTSenvironment variable to match your preferred server arguments (defaults are set to"-quit -batchmode -nographics -dedicated") - Optionally set the
SEVEN_DAYS_TO_DIE_CONFIG_FILEenvironment variable to a different configuration file (default is/app/.local/share/7DaysToDie/serverconfig.xml) - Mount
/steamcmd/7dtdand/app/.local/share/7DaysToDiesomewhere on the host to keep your data safe (first path has the server files, while the second path has the config and save files) - Run the server once to generate the default configuration file, then optionally edit it at
/app/.local/share/7DaysToDie/serverconfig.xmlto your liking
Make sure that the 7D2D serverconfig.xml file has the same server and telnet password as the one you've set in .env file
| .ev | serverconfig.xml |
|---|---|
| SEVEN_DAYS_TO_DIE_SERVER_PASSWORD=testPassword | <property name="ServerPassword" value="testPassword"/> |
SEVEN_DAYS_TO_DIE_START_MODE. This determines if the server should update and then start (mode 0), only update (mode 1) or only start (mode 2)) The default value is "0".
| Argument | Value | Description |
|---|---|---|
| SEVEN_DAYS_TO_DIE_START_MODE | 0 (Default) | server should update and then start |
| SEVEN_DAYS_TO_DIE_START_MODE | 1 | server should only update |
| SEVEN_DAYS_TO_DIE_START_MODE | 2 | server should only start |
You should also enable telnet and modify the SEVEN_DAYS_TO_DIE_TELNET_PORT and SEVEN_DAYS_TO_DIE_TELNET_PASSWORD environment variables accordingly, so the container can properly send the shutdown command to the server when the proper signal has been received (it uses telnet for this).
SEVEN_DAYS_TO_DIE_UPDATE_CHECKING is "0"
Fully automatic updates(default = disabled). Once a server update hits Steam, it'll restart the server and trigger the automatic update. You can enable this by setting SEVEN_DAYS_TO_DIE_UPDATE_CHECKING to "1".
You can also use a different branch via environment variables. For example, to install the latest experimental version, you would simply set SEVEN_DAYS_TO_DIE_BRANCH to latest_experimental (this is set to public by default).
If using Docker for Windows and the File System passthrough option, make sure to add the git repo drive letter as a shared drive through the Docker GUI.
See LICENSE
- telnet password seems to fail if other than alphanumeric (a-A, z-Z, 0-9)
- Run docker-compose config to check if you properly set things up in docker-compose file