Updating Wings

Updating Wings gets you bug fixes, security patches, and new features. Read the release notes, back up your Wings configuration, and check Panel/Wings version compatibility before updating.

What restarts?

Game server containers run independently of Wings and normally keep running during a Wings-only restart. Console connections, server controls, and SFTP are interrupted while Wings is unavailable. Docker, host OS, and game updates are separate operations and may require stopping games.

If you use the Panel's All-in-One image or package, follow Updating the Panel instead. Its update includes Wings; there is no separate AIO wings Compose service to update.

Pick the method matching how you installed Wings:

Return to the directory containing your Wings compose.yml. Pull the latest images and recreate the stack:

docker compose pull
docker compose up -d
docker compose ps
docker compose logs --tail 50

Docker handles the restart as part of up -d. Keep the existing configuration and data mounts. Wings in a container cannot upgrade itself from the Panel.

Wings 1.2.6 changed the Compose file to share the host PID and cgroup namespaces (pid: host, cgroup: host), which Wings uses to reach server containers for bandwidth limits, resource stats and CFS burst. An existing compose.yml is not updated by docker compose pull; add the two lines to the wings service yourself, or download the file again. If you use bandwidth limits on Wings 1.2.6 or 1.2.7, set docker.bandwidth.backend to container when you add pid: host, because the Wings container does not hold the capabilities the default auto choice then needs. From Wings 1.2.8, auto checks for those capabilities and uses the helper container without them.

After updating, check Admin → Nodes → (your node) → Overview for the Wings version, then open a game console and confirm it reconnects.