Updating your Portainer Server

To update to the latest version of Portainer Server, use the following commands to stop then remove the old version. Your other applications/containers will not be removed.

docker stop portainer

docker rm portainer

Now that you have stopped and removed the old version of Portainer, you must ensure that you have the most up to date version of the image locally. You can do this with a docker pull command:

docker pull portainer/portainer-ce:2.21.5

Finally, deploy the updated version of Portainer:

docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.21.5

docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:2.21.5 --sslcert /path/to/cert/portainer.crt --sslkey /path/to/cert/portainer.key

The newest version of Portainer will now be deployed on your system, using the persistent data from the previous version, and will also upgrade the Portainer database to the new version.

When the deployment is finished, go to https://your-server-address:9443 or http://your-server-address:9000 and log in. You should notice that the update notification has disappeared and the version number has been updated.

Agent-only upgrade

To update to the latest version of Portainer Agent, use the following commands to stop then remove the old version. Your other applications/containers will not be removed.

docker stop portainer_agent

docker rm portainer_agent

Next, pull the updated version of the image:

docker pull portainer/agent:2.21.5

Finally, start the agent with the updated image:

docker run -d -p 9001:9001 --name portainer_agent --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker/volumes:/var/lib/docker/volumes portainer/agent:2.21.5

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 update path might work, we recommend that all update paths are tested and validated on a non-critical system before applying them to your production systems.

Update order

In general, we recommend updating your Portainer Server deployment before you update 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.

Updating Portainer

From within Portainer

From 2.19, Business Edition users are able to update their Portainer installation directly from within Portainer. To do so, click the Update now link in the update notification in the bottom left of the Portainer UI.

In the confirmation dialog, click Start update to proceed with the update.

Manually update Portainer

If you would prefer to manually update your Portainer installation, choose your platform then follow the instructions:

If you are coming from the Portainer 1.x branch, there are steps you must follow in order to update successfully:

Update the Portainer Agent

To update the standard (non-Edge) Portainer Agent, you can find instructions in the above platform-specific links (Docker Standalone, Docker Swarm, and Kubernetes).

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