Update PhValheim¶
Keep your existing data and backup volumes when replacing the container. Your worlds and database live there.
Docker Compose¶
From your Compose folder:
Use theoriginalbrian/phvalheim-server:latest to follow official releases, or a version such as :2.59 to choose a specific release. Read the release notes before upgrading.
The startup process applies database migrations. Large upgrades can take longer; let them finish before treating a temporarily unavailable UI as a failed upgrade.
Update worlds and clients too¶
A new container does not mean every world's installed files have been rebuilt. Update your worlds from the dashboard when the release calls for it, then ask players to sync through the PhValheim client.
For 2.59: world update plus client sync delivers Companion 1.0.6, including its late join-code recovery dialog.
Unraid or Kubernetes¶
Pull the desired image through your platform and recreate the container or roll out the workload with the same persistent storage. Keep the admin UI private and wait for migrations to finish.
Keep a recovery copy
Preserve your persistent data and backups before an upgrade. A world backup is not a full copy of the database, settings or Vibes projects in /opt/stateful.