Releases: portainer/portainer
Release 2.21.1
oscarzhou-portainer
Oscar Zhou
What’s Included:
- Changes from 2.21.0:
- Fixed an issue where Portainer would crash when cloning a large Git repository
- Introduced a JWT revocation mechanism to revoke JWTs after logout
- Fixed an issue when re-creating a container on Docker 24
Release 2.21.0
This is our first Long-Term Support (LTS) release, which includes all the changes that have been added up to the 2.20.3 release, as well as various fixes aimed at enhancing the stability and scalability of Portainer.
What’s Included:
- Changes from 2.20.x:
- This LTS release incorporates all the features, improvements, and bug fixes from the 2.20.x series of releases.
- For detailed information about the changes included in the 2.20.x releases, please refer to the [2.20.x release notes](https://docs.portainer.io/v/2.20/release-notes).
New in this Release:
- Stability Improvements: Various fixes have been applied to increase the overall stability of Portainer.
- Scalability Enhancements: Specific adjustments have been made to improve the usage of Portainer at scale, ensuring better performance and reliability in larger environments.
- Security: Critical and high security vulnerabilities (CVEs) associated with dependencies shipped within the Portainer images have been addressed. This includes updates to key components like the Docker client and kubectl to ensure a secure environment.
Please review the sections below for more details on deprecated features included in this LTS release.
Deprecated Capabilities and Features:
- We’re deprecating the platform and architecture-specific images named using the convention
<platform>-<arch>-<version>in favor of the newer convention<version>-<platform>-<arch>. This change ensures standardization and consistency across our software distribution. In the future, we’ll only build and publish images using the new tag convention.
Release 2.21.0-rc2
This new release candidate build fixes a bunch of critical and high security vulnerabilities (CVE), mostly associated with the dependencies that are shipped within the Portainer images.
Release 2.21.0-rc1
This is our first Long-Term Support (LTS) release, which includes all the changes that have been added up to the 2.20.3 release, as well as various fixes aimed at enhancing the stability and scalability of Portainer.
What’s Included:
- Changes from 2.20.x:
- This LTS release incorporates all the features, improvements, and bug fixes from the 2.20.x series of releases.
- For detailed information about the changes included in the 2.20.x releases, please refer to the [2.20.x release notes](https://docs.portainer.io/v/2.20/release-notes).
New in this Release:
- Stability Improvements: Various fixes have been applied to increase the overall stability of Portainer.
- Scalability Enhancements: Specific adjustments have been made to improve the usage of Portainer at scale, ensuring better performance and reliability in larger environments.
Please review the sections below for more details on deprecated features included in this LTS release.
Deprecated Capabilities and Features:
- We’re deprecating the platform and architecture-specific images named using the convention
<platform>-<arch>-<version>in favor of the newer convention<version>-<platform>-<arch>. This change ensures standardization and consistency across our software distribution. In the future, we’ll only build and publish images using the new tag convention.
Release 2.20.3
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
Release 2.20.2
2.20.2
See Upgrading Portainer instructions.
Overview of Changes
Introducing the new Portainer CE 2.20.2 release. This is an STS (Short-Term Support) release.
As you gear up for the transition to Portainer CE 2.20.2, 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
Resolved CVEs
- Resolved CVE vulnerabilities for Windows images portainer/portainer#11716
- Updated kubectl to resolve CVEs. portainer/portainer#11741
- Resolved CVE vulnerabilities for docker binary portainer/portainer#11717
- Resolved CVE vulnerabilities for protobuf portainer/portainer#11718
- Resolved CVE vulnerabilities for crypto portainer/portainer#11719
- Updated k8s.io/apiserver and Helm to resolve CVEs. portainer/portainer#11740
- Resolved CVE vulnerabilities for containerd
- Updated Docker client library to resolve CVEs. portainer/portainer#11738
- Resolved CVE vulnerabilities for otelgrpc
- Resolved CVE vulnerabilities for stdlib portainer/portainer#11720
- Resolved CVE-2024-29296 by creating uniform response time for login attempts. portainer/portainer#11736
- Resolved a CVE regarding data encryption. portainer/portainer#11737
- Updated Docker Compose to resolve CVEs. portainer/portainer#11739
Edge
- Resolved an issue with the edge post initiation migration runner to ensure it runs migrations at the appropriate time, when connection between an edge environment and Portainer server has been established. portainer/portainer#11733
Docker
- Resolved an issue that caused errors when users attempted to connect to their Docker environment via API using HTTPS portainer/portainer#11721
- Provided info text in the UI to clearly explain environment variables stack.env file usage when deploying Docker stacks via Git vs. other methods. portainer/portainer#11732
Kubernetes
- Ensured confirmed support of vanilla Kubernetes 1.30 clusters. portainer/portainer#11730
- Resolved an issue with Kubernetes environments that have a significant number of services where the Dashboard services panel never completed loading and the loading spinner was indefinitely displayed. portainer/portainer#11734
Portainer
- Fixed an issue introduced in 2.20.0 where a user logged in using external SSO could no longer create a Portainer API access token. portainer/portainer#11731
- Fixed an issue where redeploying a git-based deployment failed due to the target path already existing portainer/portainer#11722
- Resolved an issue where pending actions to be run on environments would still be considered for deleted environments (although not actually run). portainer/portainer#11735
- Resolved issue where containers that exited with code 0 were incorrectly marked as failed deployments portainer/portainer#11724
- Introduced an additional option to automatically detect the authentication style for OAuth portainer/portainer#11725
API Changes
- Fixed the content type for responses from the API endpoint used for token generation portainer/portainer#11723
Modified endpoints
-
PUT/settings Update Portainer settingsParameters
Added: body.OAuthSettings.AuthStyleReturn Type
Added: OAuthSettings.AuthStyle -
GET/settings Retrieve Portainer settingsReturn Type
Added: OAuthSettings.AuthStyle -
PUT/settings/default_registry Update Portainer default registry settingsReturn Type
Added: OAuthSettings.AuthStyle -
POST/users/{id}/tokens Generate an API key for a userReturn Type
Added: apiKey Added: rawAPIKey
Release 2.19.5
2.19.5
See Upgrading Portainer instructions.
Overview of changes
New Portainer CE 2.19.5 release
Portainer
- Resolved CVE-2024-29296 by creating uniform response time for login attempts
Release 2.20.1
2.20.1
See Upgrading Portainer instructions.
Overview of changes
Introducing the new Portainer CE 2.20.1 release. This is an STS (Short-Term Support) release.
As you gear up for the transition to Portainer CE 2.20.1, 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
Important Note Regarding Docker 26 Support
Please be aware that support for Docker 26 is provided on an "as-is" basis and is primarily driven by best-effort principles. Minimal regression testing has been conducted to ensure basic functionality. Users should proceed with caution and report any issues they encounter.
Docker
- Resolved an issue where Docker 25/26 API changes affected container-related pages and image size display portainer/portainer#11504
Kubernetes
- Resolved an issue where deploying GitOps edge stacks on a Kubernetes edge device resulted in error portainer/portainer#11503
- Resolved an issue where the secret owner migration process could lead to a deadlock, preventing the HTTP(S) server from starting. portainer/portainer#11501
Portainer
- Fixed an issue where local stacks were being overwritten by orphaned stacks with the same name in the regular stack listing page portainer/portainer#11502
Release 2.20.0
2.20.0
See Upgrading Portainer instructions.
Overview of changes
Introducing the new Portainer CE 2.20.0 release. This is an STS (Short-Term Support) release.
As you gear up for the transition to Portainer CE 2.20.0, 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
Breaking Changes
- Introduced a requirement to specify the current user's password when adding an API token via the UI or the POST /users/{id}/tokens API endpoint.
- Fixed issue when deploying Docker stacks from Git-based custom templates where a user could edit the content via the web editor, when they should only have been able to deploy the content from Git.
Deprecation Notice
- DEPRECATED API endpoint GET /kubernetes/{id}/namespaces/{namespace}/configuration. Following Portainer 2.19 split of K8s ConfigMaps and Secrets to two UI tabs and K8s API proxy use, the original endpoint combining both resource types is marked deprecated.
- DEPRECATED API endpoint GET+POST /endpoints/{id}/kubernetes/helm/repositories, MOVED Helm UI option to Advanced Deployment/Create from Manifest screen + now allow users to delete their Helm repos. New endpoint GET+POST /users/{id}/helm/repositories added.
Resolved CVEs
- Updated various packages to resolve CVEs. portainer/portainer#9224
- Resolved CVEs for Portainer agent
- Resolved CVEs for Portainer CE and BE
Edge
- Fixed issue where admin users were unable to update a Git-based edge stack created by another user.
- Fixed issue where the "Retry deployment" toggle did not persist when editing an edge stack.
- Fixed issue clearing logs for edge jobs, addressing an error related to the absence of the specified directory
- Resolved an issue by implementing timeouts for the agent during snapshot building, preventing it from getting stuck indefinitely or taking excessive time in unresponsive Docker daemon scenarios
- Fixed an issue where the Edge Agent was resetting EndpointId to 0 and polling global-key incorrectly when disconnected from Portainer server, even with disabled edge compute features
- Fixed an issue where a dynamic edge group would erroneously create a stack even if no environment was present
Swarm
- Updated the documentation link for Swarm agent setup in the UI to ensure it directs users to the correct documentation.
- Updated the Quick Setup wizard to provide a more accurate message, eliminating misleading connection failure notifications when adding the local environment via Agent deployment.
Docker
- Fixed issue where Docker Images List breaks when an image has no tags.
Kubernetes
- Updated the version of the kubectl client in the kubectl shell console. portainer/portainer#11303
- Fixed the stripping of labels from certain Kubernetes resources - Ingress, ConfigMap or Secret - when form-editing them. portainer/portainer#11147
- Resolved an issue where, on adding a Helm repo, a timeout could sometimes occur. portainer/portainer#11137
- Resolved an issue where the upgrade to BE from CE within Portainer on MicroK8s was failing because the wait time was too short.
- Fixed an issue where namespaces 'set to system' from within Portainer weren't being detected as system. portainer/portainer#11146
- Fixed 'Unable to determine which association to use to convert form' error when adding a service to a Kubernetes pod that had been deployed external to Portainer. portainer/portainer#11136
- Corrected a minor UI issue introduced in 2.19.0, where, on create of Kubernetes application, if the user scrolled down and clicked 'Add persisted folder' without populating name and image fields, the focus would jump up to the first empty required field. portainer/portainer#11155
- Fixed an issue introduced in 2.19 in the ConfigMaps and Secrets lists where a check was no longer made against them for deployments of type Pod and hence an 'Unused' badge in those instances was then not shown. portainer/portainer#11145
- Fixed a 'this.formValues.Services is undefined' error that was shown when editing a pod created via manifest. portainer/portainer#11152
- Resolved an issue where ConfigMaps and Secrets created via manifest were incorrectly shown with the 'External' badge. portainer/portainer#11169
- Corrected showing of a blank screen when editing a Kubernetes application that had been deployed external to Portainer, so that the Edit application screen is now shown. portainer/portainer#11161
- Introduced a per-user option to enable five-minute data caching for non-edge Kubernetes environments - to improve performance. portainer/portainer#11118
- Fixed the Kubernetes Application details screen not showing referenced resources for an app that had used 'envFrom:' in its manifest to load an entire ConfigMap or Secret as environment variables instead of referencing individual values via 'valueFrom:'. portainer/portainer#11144
- Introduced a setting to turn off the Stacks functionality within the Kubernetes side of Portainer. portainer/portainer#11119
- Renamed the Kubernetes Advanced Deployment screen to be 'Create from Manifest'. portainer/portainer#11128
- Corrected display of a very high 'CPU used' value in the Kubernetes Cluster details screen when micro-CPU units were being used. portainer/portainer#11154
- DEPRECATED API endpoint GET+POST /endpoints/{id}/kubernetes/helm/repositories, MOVED Helm UI option to Advanced Deployment/Create from Manifest screen + now allow users to delete their Helm repos. New endpoint GET+POST /users/{id}/helm/repositories added. portainer/portainer#11127
- Resolved issues that occurred around editing a Kubernetes application when a namespace had resource quotas set, where the application's (pre-edit) existing resource usage was not being taken into account. portainer/portainer#11143
- Introduced a change so that, on deletion of an ECR or other registry, any related Kubernetes registry secret will now be removed. Note that this type of secret is auto created when assigning a registry to a namespace in a Kubernetes environment. portainer/portainer#11158
- Migrated the Kubernetes Application Details screen's YAML, Events and Containers sections plus any of the screen's remaining code from Angular to React. portainer/portainer#11121
- Fixed an issue around the display of incorrect search results for Kubernetes applications that are exposed via an ingress. portainer/portainer#11160
- Corrected the Kubernetes Volume Details screen to show the Shared Access Policy of the Volume rather than (erroneously) of the StorageClass. portainer/portainer#11163
- Corrected the deploying of a Kubernetes Daemonset with shared storage so that RWX access is granted to the Persistent Volume Claim, as relevant. portainer/portainer#11168
- Migrated the Kubernetes Cluster Setup screen from Angular to React and improved loading of its elements. portainer/portainer#11122
- Introduced a change so that, on assigning a user access to a Kubernetes environment that is down, the access is enabled when the environment next connects. portainer/portainer#11157
- Corrected the display of the 'Allow resource over-commit' setting in Portainer CE, which was showing as off even though the functionality has always operated as though it is on. Note that no actual changes to functionality have been made. portainer/portainer#11142
- Fixed a console error that could arise in the Kubernetes Add/Edit Application screen when updating resource sliders. [#11159](https://github.com/portainer/portainer/i...
Release 2.19.4
2.19.4
See Upgrading Portainer instructions.
Overview of changes
New Portainer CE 2.19.4 release
Swarm
- Resolved the inability to change the replica set for a swarm service, addressing errors related to invalid CredentialSpec (A refresh of your browser cache may be required)
#10702