Starbound

Simple to set up starbound server.

Running the server

docker run --detach --name starbound --publish 21025:21025/tcp hetsh/starbound

Stopping the container

docker stop starbound

Updates

This image contains a specific version of the game and will not update on startup, this decreases starting time and disk space usage. Version number is the manifest id that can also be found on SteamDB. This id is updated hourly.

netcat necessity

The Starbound Dedicated Server requires a purchased copy of Starbound on Steam. To avoid leaking my Steam credentials there is no other way (to my knowledge) than query the credentials during the RUN statement. This is realized with a quick client and server setup using netcat. netcat is immediately purged from the image after the credentials have been transferred.

Creating persistent storage

MP="/path/to/storage"
mkdir -p "$MP"
chown -R 1370:1370 "$MP"

1370 is the numerical id of the user running the server (see Dockerfile). Start the server with the additional mount flag:

docker run --mount type=bind,source=/path/to/storage,target=/starbound ...

Automate startup and shutdown via systemd

The systemd unit can be found in my GitHub repository.

systemctl enable starbound@<port> --now

Individual server instances are distinguished by host-port. By default, the systemd service assumes /apps/starbound/<port> for persistent storage and /etc/localtime for timezone. Since this is a personal systemd unit file, you might need to adjust some parameters to suit your setup.

Fork Me!

This is an open project (visit GitHub). Please feel free to ask questions, file an issue or contribute to it.