Upgrading Portainer

Portainer releases contain new features and bug fixes so it's important to keep your installation up to date. We have tested and validated all Portainer version upgrades from 2.0.0 up to the latest release.

While it's possible that an untested unvalidated upgrade path might work, we recommend that all upgrade paths are tested and validated on a non-critical system before applying them to your production systems.

We added a backup and restore feature to Portainer BE 2.7 and strongly recommend that you take a backup of your Portainer instance before upgrading.

Starting with CE 2.9 and BE 2.10 Portainer is HTTPS enabled by default and uses port 9443 to serve the UI. HTTP can still be enabled on port 9000 if required.

Upgrade order

In general, we recommend upgrading your Portainer Server deployment before you upgrade the Portainer Agents. When we release new versions of Portainer we ensure that Portainer Server is able to talk to older versions of the Agent, and in most cases the reverse is true, but in some instances we make changes to the Agent that are not fully backward compatible with older versions of Portainer Server.

Upgrading Portainer

To upgrade Portainer, choose your platform then follow the instructions:

pageUpgrading on Docker StandalonepageUpgrading on Docker SwarmpageUpgrading on Kubernetes

If you are using the Portainer Edge Agent, we have specific upgrade instructions for you:

pageUpgrading the Edge Agent

If you are coming from Portainer CE or the 1.24.x branch, we have guides for you as well.

pageSwitching to Portainer Business Edition