When an egg has an update script, customers can trigger it through a button on the client area.


Most SteamCMD-based eggs automatically update when the server starts with steamcmd update command baked into the Docker image entrypoint. Should you want to switch to manual updates, this is an example script for Garry's Mod egg. You can edit this update script to work with a lot of games very easily.

apt -y update
apt -y --no-install-recommends install curl lib32gcc1 ca-certificates

# Server Files: /mnt/server
cd /mnt/server/steamcmd

# SteamCMD fails otherwise for some reason, even running as root.
# This is changed at the end of the install process anyways.
chown -R root:root /mnt
export HOME=/mnt/server

# Optional if you want to add functionality to the beta toggle
if [ "$BETA" = true ]; then
    echo "Updating to beta branch..."
    ./steamcmd.sh +login anonymous +force_install_dir /mnt/server +app_update 4020 validate -beta dev +quit
    echo "Updating to normal branch..."
    ./steamcmd.sh +login anonymous +force_install_dir /mnt/server +app_update 4020 validate -beta public +quit

echo "Done."


With the script example above, you need to set the appropriate container and entrypoint.

Disabling automatic updates

You'll want to make sure you disable the automatic updates in the egg, continuing to use Garry's Mod as our example: you can disable automatic updates by adding auto_update 0 into the server's startup parameters. You can make this an optional startup parameter or hardcode it into the egg to disable updates by default for all servers.

Example of the flag in use

Example of the flag in use

Docker images for most SteamCMD eggs will have an egg variable AUTO_UPDATE that you can add to the egg to toggle off automated updates on startup. The variable value of 0 would disable updates and 1 on the other hand will enable them.

View all available guides, chat with the WISP community on Discord, or email support, should you require assistance.