This image will always install/update to the latest steamcmd and Valheim server, all you have to do to update your server is to redeploy the container.
Also note that the entire /steamcmd/valheim can be mounted on the host system, which would avoid having to reinstall the game when updating or recreating the container.
- Optionally set the
VALHEIM_SERVER_STARTUP_ARGUMENTSenvironment variable to match your preferred server arguments (defaults are set to"-quit -batchmode -nographics -dedicated") - Mount
/steamcmd/valheimand/app/.config/unity3d/IronGate/Valheimsomewhere on the host to keep your data safe (first path has the server files, while the second path has the config and save files)
You can control the startup mode by using VALHEIM_START_MODE. This determines if the server should update and then start (mode 0), only update (mode 1) or only start (mode 2)) The default value is "0".
One additional feature you can enable is fully automatic updates, meaning that once a server update hits Steam, it'll restart the server and trigger the automatic update. You can enable this by setting VALHEIM_UPDATE_CHECKING to "1".
You can also use a different branch via environment variables. For example, to install the latest experimental version, you would simply set VALHEIM_BRANCH to latest_experimental (this is set to public by default).
NOTE: Check the Dockerfile in the official repository for more environment variables, such as setting a server password, server admins and controlling server visibility.
See LICENSE