Upgrade CapRover
In the dashboard, open Maintenance → CapRover Updates and click Install Update when a stable update is available. On older dashboards, look under Settings.
Run these commands on the Swarm manager.
Docker API requirements
If the dashboard blocks an upgrade because the host Docker API is too old, upgrade Docker Engine first, then retry from the dashboard. Before upgrading Docker Engine, check that the new Engine supports the API version selected by any dockerApiVersion override.
The dashboard compares the host’s maximum Docker API version with the target release’s requirement. The dockerApiVersion override only selects the API version Captain uses for its own calls. We develop and test CapRover against the default API version. An upgrade that works with a lower API version on one release offers no guarantee for future releases.
Manual upgrade with an override
Use this procedure only if your current CapRover installation already runs with a dockerApiVersion override. Updating the captain-captain service directly bypasses CapRover's compatibility check. Captain may fail to start, leaving the dashboard unavailable, or operations such as app deployments may fail after startup. Proceed at your own risk and be prepared to verify the upgrade and recover the server.
-
Back up CapRover and your application data. Connect to a Swarm manager over SSH and record the current image reference, including its digest if present.
docker service inspect --format '{{.Spec.TaskTemplate.ContainerSpec.Image}}' captain-captain -
Replace
TARGET_VERSIONwith the exact CapRover release tag and update the service.docker service update --image caprover/caprover:TARGET_VERSION captain-captain -
Verify the version in the dashboard and check that your apps are reachable and app deployments work.
-
If the upgrade fails and the previous release can still read the current data, replace
PREVIOUS_IMAGEwith the full image reference you recorded and redeploy it. If the upgrade made incompatible data changes, restore your pre-upgrade backup on a fresh server. In the restore guide’sdocker runcommand, replacecaprover/caproverwith the full previous image reference you recorded.docker service update --image PREVIOUS_IMAGE captain-captain
Switch to edge
docker pull caprover/caprover-edge:latest
docker service update captain-captain --image caprover/caprover-edge:latest
Switch back to stable
docker service update captain-captain --image caprover/caprover:latest
Switching back may fail if the edge release introduced changes incompatible with the stable release.
If the update fails, see Diagnostics.