Satisfactory Server

This is a Dockerized version of the Satisfactory dedicated server.

Setup

According to the official wiki, expect to need 12GB - 16GB of RAM.

You'll need to bind a local directory to the Docker container's /config directory. This directory will hold the following directories:

• /backups - the server will automatically backup your saves when the container first starts
• /gamefiles - this is for the game's files. They're stored outside of the container to avoid needing to redownload 8GB+ every time you want to rebuild the container
• /saved - this contains the game's blueprints, saves, and server configuration

Before running the server image, you should find your user ID that will be running the container. This isn't necessary in most cases, but it's good to find out regardless. If you're seeing permission denied errors, then this is probably why. Find your ID in Linux by running the id command. Then grab the user ID (usually something like 1000) and pass it into the -e PGID=1000 and -e PUID=1000 environment variables.

Run the Satisfactory server image like this:

docker run -d --name=satisfactory-server -h satisfactory-server -e MAXPLAYERS=4 -e PGID=1000 -e PUID=1000 -e STEAMBETA=false -v /path/to/config:/config -m 16G --memory-reservation=12G -p 7777:7777/udp -p 15000:15000/udp -p 15777:15777/udp wolveix/satisfactory-server:latest

Docker Compose

If you're using Docker Compose:

version: '3'
services:
    satisfactory-server:
        container_name: 'satisfactory-server'
        hostname: 'satisfactory-server'
        image: 'wolveix/satisfactory-server:latest'
        ports:
            - '7777:7777/udp'
            - '15000:15000/udp'
            - '15777:15777/udp'
        volumes:
            - '/path/to/config:/config'
        environment:
            - MAXPLAYERS=4
            - PGID=1000
            - PUID=1000
            - STEAMBETA=false
        restart: unless-stopped
        deploy:
          resources:
            limits:
              memory: 16G
            reservations:
              memory: 12G

Kubernetes

If you are running a Kubernetes cluster, we do have a service.yaml and statefulset.yaml available under the cluster directory of this repo.

If you are using Helm, you can find charts for this repo on ArtifactHUB. The k8s-at-home helm chart for Satisfactory can be installed with the below.

Some suggested default values.yaml for the k8s-at-home chart - check out the vaules.yaml for full defaults, and the common chart for more values options.

values.yaml

env:
    # Environmental variables as below can be passed in this yaml block
    AUTOPAUSE: "true"
    MAXPLAYERS: 3

service:
    main: # Example setup for a LoadBalancer with an external IP
          # MetalLB for example could be used if a Loadbalancer is not provided by your provider
        type: LoadBalancer # Setting an external IP for simple port forwarding
        externalTrafficPolicy: Cluster
        loadBalancerIP: "192.168.2.200" # IP of the satisfactory server

persistence:
    config: # Config/save data stored here
        enabled: true

    server-cache: # Game files stored here
        # This is seperated to allow for backing up only game/config data
        enabled: true

The values.yaml could then be installed to your Kubernetes cluster with the below

helm repo add k8s-at-home https://k8s-at-home.com/charts/
helm repo update
helm install satisfactory k8s-at-home/satisfactory -f values.yaml

Environment Variables

Loading Your Save

To upload your save, connect to the server using the in-game Server Manager. From here, navigate to the save manager. Upload the save, then load it.

Experimental Branch

If you want to run a server for the Experimental version of the game, set the STEAMBETA environment variable to true.

How to Improve the Multiplayer Experience

The Satisfactory Wiki recommends a few config tweaks to really get the best out of multiplayer. These changes are already applied to the server, but they need to be applied to your local config too:

• Press WIN + R
• Enter %localappdata%/FactoryGame/Saved/Config/WindowsNoEditor
• Copy the config data from the wiki into the respective files
• Right-click each of the 3 config files (Engine.ini, Game.ini, Scalability.ini)
• Go to Properties > tick Read-only under the attributes

Known Issues

• The container is run as root. This is pretty common for Docker images, but is bad practice for security reasons. This change was made to address permissions issues
• The server log will show various errors; most of which can be safely ignored. As long as the container continues to run and your log looks similar to the example log, the server should be functioning just fine: example log