Game not getting updated even with SKIPUPDATE=fales

[Chaoschaot232]

Like title says the game server has to check for an update every time it does it's daily restart at 6 AM at my local time zone but a few days ago this didn't happened but why? I do not need a server restart when this does not include/mean a full check if there is an update out there or not.

I didn't used SKIPUPDATE=false from the beginning but it is set to "false" by default so normally no needed to be added.

Now the main question is what's causing the missing update check for a new game version? Because a server restart for me means that the games goes into shutdown mode, saving the world, kicking out connected players and then ends it's runnable which then triggers the container to go into the restart state, doing it's job checking for a new game version and then starts the game.

So something goes wrong within the container which doesn't seems todo a (forced) restart. Would be nice to get any help with this so that I know what went wrong here maybe at my end or if it's docker fault. If the game restart itself doesn't triggers a full container restart it would be nice to be implemented. For now I am going to disable the server restart as it's no use if it doesn't triggers itself the update check because I am not every time be able to hookup to the console and manually restart the container :(

Here is the docker-compose.yml which needed also to be valid for the latest docker version which no longer supports the "version" tag as this is marked as deprecated.

services:
  sf-server:
    container_name: sf-server
    restart: unless-stopped
    image: 'wolveix/satisfactory-server:latest'
    ports:
    - xxx:7777/tcp
    - xxx:7777/udp
    - xxx:8888/tcp
    volumes:
    - /home/xxx:/config
    environment:
    - MAXPLAYERS=6
    - PGID=xxx
    - PUID=xxx
    - ROOTLESS=false
    - STEAMBETA=false
    - MAXOBJECTS=3000000
    - SKIPUPDATE=false
    - AUTOSAVENUM=5
    deploy:
      resources:
        limits:
          memory: 16G
        reservations:
          memory: 8G

[wolveix]

Hey @Chaoschaot232. A few things to note. The daily restart is part of the game itself, not this container image. It is a necessary function of the core game's functionality according to the Coffee Stain developers.

Regarding the update check, I've just verified that it's working as expected. It's been a while since I've played the game, but if I recall correctly, the container doesn't do a full restart when the game restarts, it just restarts the in-game server. If that is still the case, then the game updates wouldn't trigger.

You didn't fill out the full issue template, so I'm missing a lot of key information here, but you likely just need to automate full daily container restarts yourself through your server.

It's also worth nothing that the in-game restarts should not require any human intervention. If yours do, then something is very wrong.

[Chaoschaot232]

Hey @wolveix . Thanks for the response.

The ingame restarts working like intended, it's more that normally, when something does a restart within a container, that the entire container is getting restarted like with that one from minecraft which I use. As long as the main process isn't fully going down from what I know the container itself isn't going to restart fully, triggering steamcmd to update the game.

Indeed I would then need something to restart the entire container automatically, maybe cron can help me here 🤔