Docker 7DTD Server with LinuxGSM (backups/monitoring/mods)

Tags: docker, linuxgsm, automation, backups, hosting

Containerizing the server keeps updates and dependencies tidy. LinuxGSM adds health checks, backups, and mod workflows on top.

Container layout

• Image: Debian/Ubuntu base with linuxgsm.sh installed as sdtdserver user.
• Volumes: map /home/sdtdserver/serverfiles, /home/sdtdserver/.local/share/7DaysToDie, and /home/sdtdserver/logs to the host.
• Ports: expose 26900–26902 UDP/TCP (adjust if running multiple instances).

Deploy steps

1) Build or pull an image that installs LinuxGSM and runs ./linuxgsm.sh sdtdserver + ./sdtdserver install on first start. 2) Place serverconfig.xml and serveradmin.xml in the mapped config volume. 3) Add mods by mounting a Mods/ folder into serverfiles/Mods. 4) Start the container; LinuxGSM will bootstrap updates.

Backups and monitoring

• Schedule ./sdtdserver backup via cron inside the container or through the host. Store archives off-container.
• Enable LinuxGSM alerts (Discord/Telegram/email) for crash and update notifications.
• Use ./sdtdserver monitor with a healthcheck script to restart the server if the query port stops responding.

Updating cleanly

• ./sdtdserver update inside the container pulls new builds without rebuilding the image.
• For image-level updates (OS patches), rebuild and recreate the container while keeping volumes intact.

Tips for mods

• Keep mod versions in a separate mounted folder under source control to track changes.
• Validate prefab packs in staging before going live to avoid corrupting the live save.