marcsbrooks/docker-scum-server repository overview

⁠DEPRECATED

Due to latest changes in docker-steamcmd-wine⁠ you now can configure the game options⁠ using a Docker mount rendering the need for game embedded Docker image.

The documentation below has been updated to reflect this.

⁠Starting the container

Once you have successfully pulled the repository run:

$ docker run -d --network host marcsbrooks/docker-steamcmd-wine:latest --mount type=bind,src=path/to/mount/file,dst=/var/run/docker-env

⁠Accessing the container

$ docker exec -it <container-id> /bin/bash

⁠Game server defaults

The container comes with a vanilla installation of SCUM Dedicated Server⁠ which is configured to support up to 3 players and broadcasts the server name "SCUM Server". The following ports need to be opened in your router (NAT) to ensure traffic between remote clients and the local server is routed correctly.

⁠Ports to open

⁠Managing the game server

The following command can be executed within the Docker container:

$ service game-server {start|stop|restart}

⁠Overriding game sources

In cases where you have an existing game set-up (e.g. INI configurations⁠) follow the steps below:

⁠Copy the files to the container

$ docker cp ServerSettings.ini <container-id>:/usr/games/Steam/steamapps/common/SCUM\ Server/SCUM/Saved/Config/WindowsServer/ServerSettings.ini
$ docker cp *.ini <container-id>:/usr/games/Steam/steamapps/common/SCUM Server/SCUM/Saved/Config/WindowsServer

⁠Restart the game server

$ docker -it <container-id> /usr/sbin/service game-server restart

⁠Networking workarounds

The most likely culprit to the "I cannot find my server.." issue is one of the following:

1. Your router NAT has limited support for UPnP (Universal Plug and Play)⁠ which results in game loopback requests being denied. To resolve this you must manually configure port range forwarding⁠ in your router to mirror the TCP/UDP ports exposed by the game server. This will ensure routing to your game server occurs within the network.
2. Your game server binds to the server internal IP vs router external (public) address. To resolve this you must add an IP alias to your server network device (see below). Once complete, you *may need to configure the game to launch using that same address thereby ensuring the correct IP is broadcasted to the game network.

(*) Entirely dependent on your network set-up (e.g. corporate vs home) and in most cases is not required.

⁠Adding an IP alias (spoofing your external IP address⁠)

$ sudo ip a add <ip-address>/24 dev <interface-name>
$ sudo sh -c "echo '<ip-address> localhost' >> /etc/hosts"

⁠Frequency of updates

Due to the inconsistent patch/release process by Gamespires⁠ this Docker container may already be out of date since I no longer follow their development cycle (or play their game). As a workaround you can build a custom container⁠ with the new game sources or ping me and I will update Dockerhub with the latest release.

https://steamdb.info/app/513710/patchnotes/⁠

⁠Additional information

• Created using docker-steamcmd-wine⁠
• Run this image in Amazon EC2⁠

⁠License and Warranty

This package is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose.

docker-scum-server is provided under the terms of the MIT license⁠

SCUM⁠ is a registered trademark of Gamepires⁠.

⁠Author

Marc S. Brooks⁠