This repository contains everything you need to start a dockerized dedicated Satisfactory server.
Some images on Docker hub are storing the server files in volumes or on the host filesystem. This is not a best practice in the Docker ecosystem as described here.
Volumes should ONLY be used for user specific configuration / files. The server files are not a part of it and should not be stored in volumes or on the host.
Imagine Coffee Stain Studios breaking the dedicated server software and you want to play with your friends. Other images would download and store the new server files in the volume. Now every time you start a new container it would read the broken server files and then crash, even if you reverted to an older image version.
It wouldn't even help to completely remove the local image due to the fact that these kind of images are using shell scripts to download and update the server files dynamically.
With this image this won't happen, due to the fact that the server files are stored as immutable data inside the container. Coffee Stain Studios broke the build? No problem! Just use the previous build id to run the old image and play with your friends!
Definetly not! Satisfactory still has the "old" multiplayer mode (through sessions and invites) which is probably less buggy than the dedicated servers.
There are only three reasons why you need a dedicated server:
- You want to play with your friends and all of you have a bad internet connection
- Your computer can't handle a second player (due to old computer components)
- You wanna play in a local network where you don't have internet access
- Docker
- docker-compose (if you don't wanna use the Docker CLI directly)
The minimum hardware requirements for running the dedicated server which are listed here.
- Download the repository to your computer or server and run the following command:
docker-compose up -d
- Make sure that the host directory that your bind mount uses has the correct permissions for the container user. Because this image runs the server executable as the
steamuser, a bind mount might not be writable for thesteamuser. If you run into this issue run the following command from the base folder of the repository:
chown -R 1000:1000 /shared
Take a look at the awesome video of Jace (one of the Community Managers @ Coffee Stain Studios) on how to set up the server ingame here.
The folks at Satisfactory wiki have a pretty neat guide on how you can upload the savegame to your server here.
Everything that you need to know regarding this Docker setup is, that you need to place the file in the shared/SaveGames directory. docker-compose will then mount the directory to the required location inside the container.
As far as I know you will be able to upload your savegame directly to the server from the game once it is implemented. Then you won't need the linked guide anymore.
- The dedicated server crashes when you use the
Rebar gun. It has already been reported here. - The dedicated server crashes when you try to mass dismantle buildings. It has already been reported here.
Checkout the Satisfactory Q&A platform for the most recent information regarding server crashes and co here.
If you found a bug in the server / ingame you can report the bug directly to Coffee Stain Studios here.
When it comes to the Docker support you can use the issue tracker of this repository.
This repository is licensed under the MIT license. You can find the exact license in the LICENSE file.