Portainer Documentation
Official WebsiteGet 5 Nodes of BE Free
Search…
2.14
Welcome
What's new in version 2.14
Release Notes
Getting Started
Introduction
Portainer architecture
Requirements and prerequisites
Install Portainer
Upgrading Portainer
Upgrading on Docker Standalone
Upgrading on Docker Swarm
Upgrading on Kubernetes
Upgrading on Nomad
Upgrading the Edge Agent
Switching to Portainer Business Edition
Using Portainer
Home
Docker/Swarm
Kubernetes
Azure ACI
Nomad
Edge Compute
Account settings
Administering Portainer
Users
Environments
Registries
Licenses
Authentication logs
Settings
Frequently Asked Questions
Portainer Concepts
Installing
Upgrading
Troubleshooting
Contributing
Advanced Topics
CLI configuration options
App templates
The Portainer Edge Agent
Access control
Reset the admin user's password
Security and compliance
Encrypting the Portainer database
Using your own SSL certificate with Portainer
Using Portainer with reverse proxies
Helm chart configuration options
Kubernetes roles and bindings
Deprecated and removed features
API
Accessing the Portainer API
API documentation
API usage examples
Get More Help
YouTube
Slack
Discord
Open a support request
Contribute to Portainer
Contribute
Build instructions
Powered By GitBook
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:
If you are using the Portainer Edge Agent, we have specific upgrade instructions for you:
If you are coming from Portainer CE or the 1.24.x branch, we have guides for you as well.
Previous
Edge Agent
Next
Upgrading on Docker Standalone
Last modified 1mo ago
Copy link
Edit on GitHub
Outline
Upgrade order
Upgrading Portainer