2.20.3

See Upgrading Portainer instructions.

Overview of changes

Introducing the new Portainer CE 2.20.3 release. This is an STS (Short-Term Support) release.

As you gear up for the transition to Portainer CE 2.20.3, our latest STS (Short-Term Support) installment, ensuring a smooth upgrade is key. We urge you to back up your configurations via the Portainer UI beforehand. This backup acts as your safety net, ensuring you can gracefully revert to the prior version or state if the new frontier proves too wild. Additionally, pore over the release notes for catching any compatibility issues, understanding deprecated functionalities, and identifying essential tweaks to your current setup. Your diligence will pave the way for a seamless update.

A Short-Term Support release can be considered as "bleeding-edge" as it will contain the latest features and functionality we've developed. The STS releases (including this one) will go through a significant amount of pre-release testing, but there may be changes that could cause regressions and features that might see further iterations. As such, if stability is a crucial concern for your setup we wouldn't recommend deploying STS releases on production environments.

Read more in our "Portainer 2.20 STS" blog post

Important Notice:

On update to this Portainer version, stacks and edge stacks will have their containers restarted after updating them. This is caused by the use of Docker Compose 2.26.1, which requires this restart. Note: If you already updated to 2.20.0, 2.20.1 or 2.20.2 previously, stacks and edge stacks that DO NOT use relative paths may already have had their containers restarted on update of them, and you would not then see a restart again.

Docker

• Resolved an issue introduced in 2.20.0 where stopped Docker containers were incorrectly shown with an Unused badge. portainer/portainer#11797

Swarm

• Resolved an issue where the Edit Container page on Swarm environments was not loading properly. portainer/portainer#11830

Kubernetes

• Resolved an issue introduced in 2.20.0 where, when a placement rule was created for a Kubernetes application, if it was not met for a node, then it would not show up in the expand rows of the Application Details Placement constraints/preferences table. portainer/portainer#11826
• Resolved an issue in the Kubernetes Applications List page where the namespace filter selection of a system namespace did not persist on refresh or revisit. portainer/portainer#11798
• Introduced a tooltip to the 'Rollback to previous configuration' button in the Kubernetes Application Details screen to explain how rollback works. portainer/portainer#11804
• Prevented a panic from occurring when mistakenly attempting to deploy a Kubernetes application and supplying a docker-compose.yaml instead of a Kubernetes manifest. portainer/portainer#11796

Portainer

• Resolved an issue where pending actions to be run on environments could end up in a panic state. portainer/portainer#11818
• Resolved an issue where the subpath of an image tag was incorrectly truncated. portainer/portainer#11831
• Resolved an issue around excessive GitHub API Portainer version checking on page loads. portainer/portainer#11795
• Resolved an issue where loading a large number of volumes took an unreasonable amount of time portainer/portainer#11829
• Resolved an issue in the agent where removing an undeployed stack resulted in errors. portainer/portainer#11828
• Corrected the title wording and some UI styling in the Authentication Logs and Activity Logs screens. portainer/portainer#11807
• Resolved an issue with deploying of containers via Portainer running on Windows Server 2022, where an error regarding CAP_AUDIT_WRITE was occurring. portainer/portainer#11805

API Changes

• No API changes in Portainer CE for 2.20.2 to 2.20.3