Release Notes
Last updated
Was this helpful?
Last updated
Was this helpful?
The following release notes are for the Business Edition of Portainer. For Community Edition release notes, refer to the .
May 9, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration and does not affect authentication for any other functionality in the cluster.
Implemented a new API route that will return logs collected from remote async environments
May 2, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration and does not affect authentication for any other functionality in the cluster.
Fixed an issue where the PORTAINER_EDGE_ID variable was not being set properly
April 15, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration and does not affect authentication for any other functionality in the cluster.
Implemented functionality to provide a method to update Team Memberships from external auth
Fixed an issue where an "edge secret is not allowed to transmit over HTTP” error could appear when pushing a change to an Edge Configuration using the API
Resolved the following CVEs:
CVE-2025-22868
CVE-2025-30204
CVE-2025-32386
CVE-2025-32387
March 25, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration and does not affect authentication for any other functionality in the cluster.
Fixed missing cluster CPU reservation readings for Kubernetes clusters (R8S-268)
Fixed data loss resulting from redeploying stacks with relative path volumes (BE-11723)
Fixed error when updating user theme settings in profile (BE-11713)
Fixed “Unable to retrieve user authorizations” error when Edge Admins visit a page inside an environment (BE-11726)
Fixed “Change container image” form disappearing from Swarm service edit page after a hard refresh (BE-11707)
Fixed some pages only displaying first section of content (BE-11708)
March 19, 2025
When viewing or editing your user profile (via My Account) an error is being thrown. A fix for this will be provided in the next patch release.
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.
Fixed an issue on Kubernetes environments where invalid deployments could fail silently
Fixed an issue on Kubernetes environments where namespaces that the user did not have access to could be shown
Fixed an issue where the select all checkbox didn't reflect the selected state
Resolved CVE-2025-22869
Optimized OAuth automatic team memberships
Fixed an issue where adding Omni nodes wasn't showing available machines
Fixed user access loss due to --disable-role-sync flag
February 27, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.
Security: Resolved CVE-2024-50338
Fixed an issue where Compose files were not interpolated with .env
Fixed an issue where team(s) added to namespace access disappeared when a new team was added to environment
Added server certificate revalidation for mTLS connections
Added a mTLS status indicator icon for Edge Agent environments
February 20, 2025
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.
Security: CVE-2025-21614, CVE-2025-21613, CVE-2024-45337, and CVE-2024-11053
Fix: Early exit optimization does not return the correct error
Fix: 2.19.5 - 2.21 Migration fails with "StorageError: invalid object"
Optimization: Investigate the web editor slowdown while typing
Improvement: Edge stack missing value warning improvement
Fix: Removing an edge stack makes the backend panic
Fix: Object not found inside the database (bucket=endpoint_relations, key=8)
Improvement: use an Edge Stack Status Update coordinator
Fix: High memory usage when counting nodes and CPUs
Fix: Unable to add environment to static Edge group
Fix: Removing an edge stack makes the backend panic
Fix: Error “failed to find local environment” occurs if there is at least one environment configured but no local environment
Fix: Bitnami Helm Charts location has moved
Fix: Edge stack "deployment received" counting is not correct with large scale deployments
Fix: Unable to deploy a git edge stack
Fix: RegistryList API operation returns password in clear text
Fix: Agent Edge stack status watcher errors on Swarm
Fix: edge_stack folder in volume is not deleted after Edge stack is removed
Fix: Swarm: Empty/incorrect value in Host column of Images list
Fix: Unpopulated Volumes Dropdown in App Templates in Portainer 2.21.4
Fix: "Select all" should select only elements of the current page
Fix: podman doesnt appear in the option to filter by platform in the homepage
Fix: Edge stack webhooks cannot be disabled once created
Fix: Unable to expand application list rows to view published URLs
Improvement: Change docs URL schema to LTS / STS
Fix: Group membership synchronization between Portainer and Azure OAuth appears to be broken
Fix: Adding environment variables to an application with a configmap moves the configmap to the secrets section and brings down the app
Improvement: Kubernetes - Rename Create from file to Create from code
Fix: Incorrect Replicated count while performing rolling restart on deployment
Fix: Kubernetes - Broken Cluster View
Fix: Podman - Unable to create an image from a container
Fix: User gets duplicated in a Team for each login, once it reaches 12 duplicates user unable to use any functions in Portainer
Improvement: Unit test the docker RBAC layer in BE
Improvement: Associating async Edge agent based devices in the waiting room outputs tunnel error
Optimization: Remove useless pending actions on startup
Fix: Edge Stack update not working
Fix: Async snapshots are discarded from the server when the agent doesn't send them
Fix: Update & Rollback schedules are not executed on standard edge agents
Fix: Edge Stack update not working
Fix: Unable to successfully update async edge stack using parallel update
Fix: Edge stack webhook does not update and pass env variables at the same time
Fix: Unable to redeploy stack if repo ref is changed
Fix: Edge settings don't persist when restarting Portainer
Fix: Can't Delete Image from Swarm Cluster
Improvement: Stabilise the overall diagnostics data collection
Improvement: Improve validations for Omni Credentials
Fix: RoleBinding and ClusterRoleBinding removal issues
Improvement: Refresh available machines when switching Omni credentials
Deprecated features
Reminder: <platform>-<arch> image tags were deprecated in 2.21
Removed features
The following API endpoints have been removed:
POST /endpoints/{id}/edge/trust
GET /edge_templates
POST /templates/file
POST /endpoints/{id}/kubernetes/helm/repositories
GET /endpoints/{id}/kubernetes/helm/repositories
GET /kubernetes/{id}/namespaces/{namespace}/configuration
POST /cloud/{provider}/cluster
GET /cloudcredentials
POST /cloudcredentials
GET /cloudcredentials/{id}
DELETE /cloudcredentials/{id}
PUT /cloudcredentials/{id}
POST /custom_templates
POST /edge_jobs
GET /cloud/microk8s/addons
POST /stacks
DELETE /edge_stacks/{id}/status/{environmentId}
POST /edge_stacks
GET /status/version
GET /status/nodes
January 21, 2025
Service pruning does not work with stacks using relative paths
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.
Displaying job executions of cron jobs are limited to 3.
Fixed issues relating to the Omni / Talos integration:
Implemented additional validation when adding Omni credentials in Portainer to ensure the Service Account key is correct, that it has an admin role, and that it is not expired.
Prevent the deletion of Omni credentials if they are still in use with an Omni environment within Portainer.
Do not apply Machine Config patches when ‘Override network settings’ is disabled.
January 15, 2025
Service pruning does not work with stacks using relative paths
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Loading Omni specific information in the Cluster Details view and configuring an existing Talos cluster is currently restricted to Portainer Admins. Environment Admins will get a forbidden error when attempting to do this. This only applies to Omni configuration, and does not affect authentication for any other functionality in the cluster.
Displaying job executions of cron jobs are limited to 3.
Added the ability to remove associated volumes when deleting a stack
Improved the performance for edge:
Optimized the server polling handler
Optimized the snapshot diff for async
Optimized AddEnvironmentToEdgeGroups()
Made the async polling handler work concurrently in an optimistic way to allow for more parallelism
Optimized the async command creation to reduce DB lookups
Optimized the concurrent Edge Stack retrieval by the agent
Optimized the Edge Stack status update by the agent
Fixed a goroutine leak in the Agent that would exhaust the resources over time
Fixed Edge Stack status updates so that it doesn’t cause wrong counts
Updated compose-unpacker so it doesn’t rely on the docker-compose binary
Fixed data races:
GetPlatform()
Docker transport
Agent stack manager
Edge auto-onboarding
Fixed potential logic problems related to edge environment configurations
Fixed the async snapshot diff logic for Kubernetes environments
Fixed the router for Kubernetes requests
Fixed a problem that prevented the assignment of multiple edge groups to async agents on association
Fixed a problem that prevented the association of async devices without groups
Fixed a problem that would cause for the edge stack local filesystem path to not be retained when using GitOps edge configs
Fixed the volume list retrieval and app template deployment when the environment snapshot doesn’t exist
Standardized the lower case string comparison method
Fixed a problem that prevented the update of edge stacks when using webhooks with async environments
Added a new feature to integrate with Sidero Omni
Added a feature behind a feature flag to disable automatic sync of the built-in Kubernetes roles
Added a 30 minutes time interval to the OAuth session timeout options
Added a new Kubernetes view for Jobs and Cron Jobs
Fixed update create from file option order
None
None
December 20, 2024
Service pruning does not work with stacks using relative paths
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
December 20, 2024
CVE-2024-45337
Fixed an issue that omitted copying the IP address in container port mapping when provided during the Edit/Duplicate operation for an existing container.
Fixed an issue with images that included files failing to build.
Fixed a resource leak that prevented the backup process from finishing under some specific circumstances.
Optimized the space used by Git repositories.
Fixed aggressive image pulling retry.
Fixed an issue where LDAP users get duplicated in a Team for each login.
December 16, 2024
Service pruning does not work with stacks using relative paths
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Added the ability to prune services while updating Compose Edge Stacks
Updated Compose to v2.31
Optimized the HTTP request/response compressor to reduce allocations and improve performance
Async Edge Agent: cleaned up executed commands to improve performance
Reduced the total locking time for the backup process and improved the error messages
Stopped preventing the server startup when docker_config/config.json file is corrupted
Added the ability for users to specify Portainer agent and updater images from their private registry when creating a remote update or rollback schedule for agents
Fixed a problem that prevented interaction with Swarm volumes
Fixed a problem that prevented the GitOps edge configurations from working properly
Fixed the missing IP binding of published ports when editing a container
Enforced timeouts for offline environments when doing parallel edge deployments
Fixed a resource leak that prevented the backup process from finishing under some specific circumstances
Removed incorrect persistence of filters when interacting with Services and Stack pages
Restored the remember functionality in the filtered stacks search results
Enforced Edge Stack naming rules
Fixed an issue with images that included files failing to build
Ensured proper Edge Stack removal after a power interruption in the Agent
Fixed an issue where Git stacks using sub-directories and environment files could not be edited
Fixed an issue where an extra network is created when deploying a stack with only external networks defined
Fixed an issue where the env_file field in Compose files were being ignored
Fixed an issue where a stack that built an image that it then referenced would fail to deploy with a "no such image" error
Ensured that the PORTAINER_EDGE_ID variable is properly exposed when using Edge Configurations
Added a new feature called Download Support Bundle
Added a new feature to enable/disable debug logging within the Portainer UI
Added a new button in the Licenses Page to support renewal
Fixed an issue where Helm status was not correctly shown for deployments
Fixed an issue where the date picker was unusable for activity logs in the dark mode
Fixed an issue where the namespace level access not being applied to teams
Fixed an issue where edge stack fails to be deleted when K8s job is set with TTL
Fixed an issue where LDAP users get duplicated in a Team for each login
Improved kapa.ai landing page
Migrated a handful of legacy Angular based Kubernetes pages to React
PUT /kubernetes/{id}/namespaces API endpoint
None
December 3, 2024
Service pruning does not work with stacks using relative paths
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Fixed an issue where Git stacks using subdirectories and environment files could not be edited.
Fixed an issue where an extra network was being created when deploying a stack with only external networks defined.
Fixed an issue where the env_file field in Compose files was being ignored.
Fixed an issue where users were unable to pull images from private registries as expected.
Fixed an issue where a stack that built an image that it then referenced would fail to deploy with a "no such image" error.
Fixed an infinite recursion issue in an RBAC route when switching users and connecting to an agent endpoint.
Fixed an issue that omitted copying the IP address in container port mapping when provided during the Edit/Duplicate operation for an existing container.
Fixed an issue with images that included files failing to build.
Fixed an issue where activity logs shown in the Portainer UI were encoded with base64.
November 20, 2024
Known issues with Docker support
Service pruning does not work with stacks using relative paths
Known issues with Podman support
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Bumped Go version to 1.23
Improved the status tracking for Kubernetes Edge Stacks
Rewrote the stack deployment code to remove the need for the docker-compose binary
Clean-up and compact user activity DB on start-up
Added the ability to prune services while deploying Compose stacks
Added a retry period to Edge Stack deployments
Fixed user authentication log sorting
Defaulted to descending timestamp order in the user activity log
Fixed user activity log sorting
Fixed aggressive image pulling retry
Relocated the GitOps TLS toggle so it’s harder to overlook
Added timeouts to OAuth requests
Fixed problem that prevented environment association in the waiting room
Fixed a problem that prevented the Docker image exporting
Improved the Kubernetes Cluster node view to display conditions
Migrated more Angular based pages to React
Fixed the following Kubernetes regressions:
Standard user can't get cluster scoped ingress controllers
CPU/Memory Limit & Reservation values not multiplied by replica count on "Applications running on this node" table
Application rollout restart isn’t functional
None
None
October 25, 2024
Ported client API negotiation changes to ensure LTS can be compatible with future Docker versions.
Improved the Edge-related API error response by including environment ID and name.
Added the display of the missing Edge stack deployment errors on the Edge stack environment status page.
Fixed an issue that prevented the removal of older files when updating an Edge configuration.
Fixed an issue that prevented consecutive updates of Swarm services from reloading the page.
October 16, 2024
Image export is not functioning
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Unable to create an image from a container
Service accounts, Cluster Roles/Bindings, Roles/Role Bindings) show system resources when toggle is off
Standard user can't get cluster scoped ingress controllers
CPU/Memory Limit & Reservation values not multiplied by replica count on "Applications running on this node" table
Application rollout restart is not functioning
Improved the Home page search speed
Improved OAuth logging to help diagnose errors
Increased the CRL request timeout in the Agent to 30s
Moved the webhook deploying logic to the background to avoid timeouts
Optimized the space used by Git repositories
Improved the Edge-related API error response by including environment ID and name
Fixed the removal of old files when doing an Edge Config update
Added the display of the missing Edge stack deployment errors on the Edge stack environment status page
Fixed the Pending status getting stuck for Edge stacks when re-associating environments
Fixed issues with Kubernetes resources not showing information correctly
Improved the overall experience for Kubernetes
None
Platform and Architecture-Specific Images:
We have removed image tags named for various architectures using the convention <platform>-<arch>. These images tags were deprecated in a previous release. This change ensures further standardization and consistency across our software distribution.
October 8, 2024
Improved home page search performance, addressing slow response times in certain environments.
Fixed an issue where the Edge admin role would be removed after login when authenticating via OAuth.
Fixed an issue where the CRL (Certificate Revocation List) request timeout may be too short, causing potential connection issues.
October 3, 2024
As part of the changes on the Kubernetes experiences, some API operations for Kubernetes management may have changed slightly.
Podman environments aren't supported by auto-onboarding script
It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa)
Support for only CentOS 9, Podman 5 rootful
Unable to create an image from a container
Applications deployed via helm chart are no longer grouped on the App list screen
Service accounts, Cluster Roles/Bindings, Roles/Role Bindings) show system resources when toggle is off
Standard user can't get cluster scoped ingress controllers
Unused label incorrectly showing on used volumes, and Used by column is blank
NaN value on Memory & CPU used bars on Node Details screen
CPU/Memory Limit/Reservation values on Applications running on this node table rounding down
Volumes created within Portainer are incorrectly labelled as External
Podman Support:
Portainer now supports Podman. It can be installed on Podman and manage Podman environments. Initial support includes Podman 5.x running on CentOS environments.
ACI Enhancements:
Enhancements to ACI management include support for GPUs, private IPs, persistence, and the ability to start, stop, and restart container instances, among other improvements.
Better Kubernetes Management Experience:
The Kubernetes management experience has been overhauled by relocating most of the logic from the client to the server, improving client speed and responsiveness. This update also introduces the ability to manage all Kubernetes resources via a simplified, abstracted API.
Security Controls for Kubernetes:
New security controls allow administrators to disable access to downloading Kubeconfig files and interacting with the Kubernetes shell for non-administrator users.
Edge Capabilities Improvements:
Enhancements to the Edge features have resulted in a more stable, performant, and reliable experience when using Edge capabilities.
Stability Improvements:
Various fixes have been applied to increase the overall stability of Portainer.
Scalability Enhancements:
Adjustments have been made to improve Portainer's performance and reliability at scale, especially in larger environments.
Security:
Critical and high-security vulnerabilities (CVEs) in dependencies shipped within the Portainer images have been addressed. Key components, such as the Docker client and kubectl, have been updated to ensure a secure environment.
Platform and Architecture-Specific Images:
We are deprecating image tags named for various architectures using the convention <platform>-<arch>. This change ensures further standardization and consistency across our software distribution.
Platform and Architecture-Specific Images:
We are removing images named using the convention <platform>-<arch>-<version>. These images were deprecated in a previous release in favor of the newer convention <version>-<platform>-<arch>. This change ensures standardization and consistency across our software distribution.
Kompose Logic:
All logic related to Kompose has been removed, following its deprecation in a previous version.
Nomad Support:
All logic related to Nomad support has been removed after it was deprecated and subsequently removed from the client in version 2.20.
September 24, 2024
Updated Linode branding to align with the new “Akamai Connected Cloud”.
Fixed an issue with stack deployment on Docker when using a .env file from a Git Repository and referencing it in the Compose file.
September 10, 2024
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
Fixed an issue with stack deployment on Docker when using environment variables in the volumes section of the Compose file
August 27, 2024
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.
Changes from 2.20.x:
This LTS release incorporates all the features, improvements, and bug fixes from the 2.20.x series of releases.
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.
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.
May 21, 2024
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.
Resolved an issue where edge configuration files were not being backed up.
Resolved an issue where device registration via the waiting room was extremely slow during large-scale edge deployment.
Resolved an issue where users were unable to remove or update an edge configuration that was pending deployment on a device.
Resolved an issue when creating a MicroK8s cluster where using a hyphen to specify an IP range had stopped working in 2.19.
Resolved an issue where the "More resources" views in Kubernetes would redirect to the Dashboard upon refresh.
Applied updates and ensured confirmed Kubernetes 1.30 support with creation of MicroK8s clusters.
Introduced an offline mode for creation of a MicroK8s Kubernetes cluster on air-gapped nodes.
May 1, 2024
Resolved CVE vulnerabilities for containerd
Resolved CVE vulnerabilities for otelgrpc
Updated OPA Gatekeeper for Pod security constraints feature in order to resolve CVEs.
Fixed a bug with 2.20 migrating of Kubernetes secrets ownership to an improved model where the migration was not being flagged as complete.
Ensured Kubernetes 1.29 is supported with Azure Kubernetes Service (AKS) provisioning of KaaS clusters.
Ensured Kubernetes 1.29 is supported with Linode Kubernetes Engine (LKE) provisioning of KaaS clusters.
April 22, 2024
Resolved CVE-2024-29296 by creating uniform response time for login attempts
April 5, 2024
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.
March 19, 2024
Introducing the new Portainer BE 2.20.0 release. This is an STS (Short-Term Support) release.
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.
Discontinued Nomad support in this release. Users won't be able to create new Nomad environments from the UI, and existing Nomad environments are hidden, ceasing their management through Portainer
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.
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 for Portainer Agent
Resolved CVEs for Portainer CE and BE
Addressed CVEs affecting Nomad, enhancing security and stability
Fixed an issue where edge stacks deployed with retry policy and failing to deploy would remain stuck indefinitely after 1 hour of retries
Fixed issue where edge stacks with GitOps enabled, would stop polling after restarting the server.
Fixed issue where confirmation modal was missing when user was trying to update edge stacks.
Resolving an issue where newer versions of images were not being pulled from the registry as expected when re-pull option was turned on.
Fixed issue where pre-pull image and retry deployment options were missing after edge stack was deployed
Fixed an issue where clicking to filter ascending/descending by a column on the waiting room page did not result in any sorting.
Fixed issue where admin users were unable to update a Git-based edge stack created by another user.
Fixed an issue where, upon disabling the waiting room feature, existing devices in the waiting room are now automatically associated to prevent them from remaining unassociated
Implemented a new "Edge Admin" role, enabling users to administer the edge compute feature without altering Portainer settings.
Fixed issue where the "Retry deployment" toggle did not persist when editing an edge stack.
Improved UX of making "GitOps Edge Configuration" stand independently, simplifying access and allowing users to effortlessly enable relative paths during configuration.
Resolved an issue where the count of configurations pushed to edge devices was inaccurately displayed. We now prevent double counting and ensure accurate representation
Updated app template version to 3.0, now supporting edge apps in templates.
Corrected the incorrect icon style for edge groups in the UI
Enhanced the tooltips in the auto onboarding page to provide clear instructions on how to use the "Edge ID" field. Users will now receive guidance on the specific command to run in the script for generating the edge ID
Resolved an issue where the waiting room remained visible in the sidebar menu despite being disabled by the administrator. The waiting room now correctly hides when disabled.
Simplified scheduler time settings by removing seconds, providing users with a more straightforward configuration experience.
Fixed issue where searching for edge groups in the waiting room returned no results
Fixed issue where non-trusted environments were incorrectly counted for static edge groups
Implemented the ability for users to upload and manage edge configurations grouped by folders, allowing seamless deployment based on matching edge group names rather than individual devices.
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
Introduced Edge App Templates and Custom Templates to address the absence of app and custom templates for edge stacks in Portainer
Fixed an issue where a dynamic edge group would erroneously create a stack even if no environment was present
Decoupled the display of Portainer API server URL and tunnel server address from the Edge Compute feature toggle, ensuring clear visibility regardless of the Edge Compute setting, addressing potential user confusion.
Resolved an issue with the Docker Swarm Service List screen where image up to date indicators were not always correct.
Fixed issue where relative path volumes in Docker Swarm environments did not update when new commits were pushed to the upstream repository and the user clicked "Pull and redeploy" in stacks with GitOps updates enabled.
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.
Introduced the ability to trigger reload of image up to date indicators in the UI.
Fixed issue where Docker Images List breaks when an image has no tags.
Resolved inconsistencies between image up to date indicators of Docker Container List, Stack List and Stack Details screens.
Introduced warning that Civo KaaS provisioning for a Kubernetes 1.27+ cluster on Extra Small node size may no longer complete as the compute resources are now too limited for required workloads.
Ensured that, when enabling addons on a MicroK8s cluster during initial set-up of that cluster, any errors that arise are now shown in the UI.
Ensured that, when enabling addons on a MicroK8s cluster post set-up of that cluster, any errors that arise are now shown in the UI.
Disabled GKE functionality's Google API client telemetry.
Resolved inconsistency in Kubernetes deployment behavior between standard and async agents regarding the 'Use namespace(s) specified from manifest' switch
Fixed an issue introduced in 2.19.0 where a Kubernetes application deployed from Git required re-entry of Git credentials when changing the deployment.
Fixed issues that occurred when creating a Kubernetes namespace after disabling cluster's over-commit setting, including "Value must be between 0 and -x." warning that was incorrectly shown.
Resolved an issue with deploying of an edge stack to a Kubernetes async device failing.
Introduced an option to enforce admin-only viewing/editing of Kubernetes Secret contents in the UI (where the user did not create that Secret).
Resolved error shown on editing a Kubernetes namespace when the cluster's 'Allow resource over-commit' setting had been turned off where the namespace had originally been created when the cluster's setting was on.
Introduced new screen for listing, searching and deleting Kubernetes Cluster Roles and their Bindings.
Introduced new screen for listing, searching and deleting Kubernetes Roles and their Bindings.
Introduced new screen for listing, searching and deleting Kubernetes Service Accounts.
Ensured Kubernetes 1.28 is supported with Linode Kubernetes Engine (LKE) provisioning of KaaS clusters.
Ensured Kubernetes 1.29 is supported with DigitalOcean Kubernetes (DOKS) provisioning of KaaS clusters.
Applied updates and ensured Kubernetes 1.29 is supported with Amazon Elastic Kubernetes Service (EKS) provisioning of KaaS clusters.
Ensured Kubernetes 1.28 is supported with Civo Kubernetes provisioning of KaaS clusters.
Ensured Kubernetes 1.28 is supported with Google Kubernetes Engine (GKE) provisioning of KaaS clusters.
Ensured Kubernetes 1.27 is supported with Civo Kubernetes provisioning of KaaS clusters.
Ensured Kubernetes 1.27 is supported with Linode Kubernetes Engine (LKE) provisioning of KaaS clusters.
Ensured Kubernetes 1.28 is supported with Azure Kubernetes Service (AKS) provisioning of KaaS clusters.
Ensured Kubernetes 1.28 is supported with DigitalOcean Kubernetes (DOKS) provisioning of KaaS clusters.
Applied updates and ensured Kubernetes 1.28 is supported with Amazon Elastic Kubernetes Service (EKS) provisioning of KaaS clusters.
Corrected access to Add Shared Credentials screen to prevent standard users from navigating to it (although note that it was already correctly disallowing add or view of credentials).
Removed the possibility of a race condition occurring on use of the eksctl binary for Amazon EKS KaaS cluster provisioning.
Applied updates and ensured confirmed Kubernetes 1.29 support with creation of MicroK8s clusters.
Corrected the grammar of a MicroK8s version retrieval error message.
Ensured confirmed Kubernetes 1.28 support with creation of MicroK8s clusters.
Introduced the ability for admins to enable the mayastor addon (that has prerequisites) for a MicroK8s cluster, and for admins and environments admins to enable or disable the mayastor addon for a MicroK8s cluster, after is has been provisioned.
Introduced the ability for admins to enable the minio addon (that has prerequisites) for a MicroK8s cluster, and for admins and environments admins to enable or disable the minio addon for a MicroK8s cluster, after is has been provisioned.
Resolved a Portainer and MicroK8s issue where, on installing Portainer Agent, the microk8s status command incorrectly shows Portainer Server as enabled. Note, this is fixed in fresh MicroK8s 1.29 installs (and is unrelated to the Portainer version).
Fixed an issue where the "Force HTTPS only" toggle in the SSL certificates section was not functioning as expected.
Fixed an issue that caused local stacks to be overwritten by orphaned stacks with the same name on the regular stack listing page
Fixed issue where users could erroneously edit web editor content in Git-based custom templates.
Improved logging of in-app Kubernetes CE to BE upgrade.
Fixed web editor errors when selecting between templates with identical Mustache variables and default values.
Added experimental feature (behind a feature flag) to stream Syslog-formatted user activity and authentication logs to an external Security Information and Event Management (SIEM) system.
Fixed issue where Bitbucket commit links were broken due to incorrect URL formatting.
Fixed an issue where a webhook error occurred during the redeployment of a stack created from a private Git repository with relative path enabled.
Fixed an issue where the cursor would jump to the end of the field after entering a character while editing environment variables for a stack.
Fixed issue where sorting images by tags in the Images view of a Docker/Swarm environment had no effect, ensuring that images are now sorted in tag order when clicking on the Tags column header.
Fixed an issue where users were unable to edit the YAML provided by a selected Custom template when deploying a stack.
Improved GitOps auto updates to prevent piling up when the deployment time exceeds the polling interval.
Fixed an issue with the Log viewer where lines that only contained numerical values were not shown.
Fixed a UI issue in Backup settings where, on reopening, they would revert to the default view after saving as S3.
Fixed an issue where triggering a non-admin container's webhook changed the permission to admin-only.
Resolved repository reference display discrepancy on deployed Environment Stacks details page
Fixed inconsistency in container counting between the environment tile on the home page and the containers tile on the environment's Dashboard.
Introducing 'Auto-Complete' branch selection for Git repositories in stack creation
Provided information text to notify users that the GPU feature supports only Nvidia graphics cards, addressing any potential confusion
Changed the "Upgrade Licenses" button to "Buy more nodes" for accurate representation of the action, as it reflects the purchase of additional licenses for expanding the number of nodes.
Resolved an issue in GitLab registry handling, ensuring that Portainer continues loading images seamlessly despite errors such as deleted repositories, preventing 401 errors from affecting the display.
Discontinued Nomad support in this release. Users won't be able to create new Nomad environments from the UI, and existing Nomad environments are hidden, ceasing their management through Portainer
Enhanced version details popup to display the current Git commit hash and specific server environment variables for improved transparency and troubleshooting.
Resolved an issue where an invalid IP address caused an error when the PORT environment variable was used during stack deployment
Fixed issue where editing stacks or edge stacks didn't display relative path information. We now ensure clarity on the mounting point used, despite users being unable to modify the relative path during the editing process
Adjusted license check-in.
Improved authentication and activity logs exported content.
Improved security by storing sensitive JWT tokens in a more secure manner, enhancing protection for user authentication in the local browser storage
Implemented improvements to restrict access to specific environment group details
Enhanced measures to prevent global admins from accessing each other's tokens through direct HTTP requests. This ensures data privacy and aligns with intended access levels in the User Interface.
Fixed an issue where the "Save Settings" button remained disabled after changing Advanced Options for a Git stack
Disabled ability to edit orphaned stacks, ensuring consistency and preventing unintended modifications from the UI.
Fixed issue where sorting by the "Updated" column in the Stacks view of a Docker environment incorrectly sorted based on the "Created" column instead.
Implemented displaying of the exit code for containers in the Portainer UI.
Fixed an issue where the client secret field appeared blank when editing an OAuth configuration under 'Settings - Authentication'.
Improved security by adding a dropdown to hide environment variables in the stack UI on the details page, preventing potential exposure of sensitive information in public or share environments.
Resolved an issue where information was missing on the registry tag view due to certain registry servers not providing manifest v1 json
Resolved an issue where hiding a container would incorrectly label the associated container image as Unused. We now ensure accurate representation and address potential user confusion and unintended image deletion.
Fixed a console error that occurred when resizing the browser window on the containers page, particularly during an active exec console session.
Resolved an issue in Container Logs with the Wrap Lines toggle on, where the log display could be mangled and end up unreadable.
Resolved an issue where adding an environment to a newly created group didn't move it from 'available environment' to 'associated environment'; this now functions correctly.
Updated Chisel to version 1.9 to facilitate the upgrade of Golang to version 1.20 for improved performance and compatibility
Updated the logging library to restore colored console logs from the Portainer binary, enhancing readability and improving visibility for users.
Corrected Swagger API documentation for the Stack image status endpoint, which should be /stacks/{id}/images_status (rather than /docker/{environmentId}/stacks/{id}/images_status).
Corrected Swagger API documentation for the Docker container, service and stack image status endpoints so they now include example responses and a status explanation.
Corrected Swagger API documentation for various /cloud (KaaS) endpoints and around an edge generate key endpoint.
Corrected Swagger API documentation for the GET /edge_update_schedules endpoint so it now describes the includeEdgeStacks parameter, and the /edge_update_schedules/active endpoint which is a POST request but was (erroneously) described as a GET request.
Fixed Swagger API documentation to accurately reflect the path where the 'environmentId' should be passed, addressing inconsistencies between the documentation and the actual implementation.
Updated Swagger API documentation to ensure consistency in property naming conventions by using PascalCase instead of camelCase.
Fixed Swagger API documentation issue where the kaas version and system version APIs erroneously shared the same swaggo ID.
Enhanced the system version API endpoint's response to now include the Portainer version type, distinguishing between Community Edition and Business Edition.
December 6, 2023
November 22, 2023
November 13, 2023
Deprecation notice of Nomad support in next minor release.
Fixed bug around Update and Rollback menu showing when Edge Compute feature is disabled.
Resolved an issue where edge group details were missing from the update and rollback table.
Resolved an issue where searching on the Update & Rollback page caused the screen to go blank
Resolved an issue where users were unable to delete any failed remote update scheduler entries.
Resolved an issue where edge stack rollback and pause updates remained stuck in the pending state
Resolved an issue where the update scheduler would stay in a "pending" state indefinitely, even when some edge agents were already running the latest version in the target edge group.
Added a deprecation notice to inform users about the upcoming removal of Nomad support in next minor release.
Fixed 'unable to upgrade' error that could potentially occur when upgrading from CE to BE.
Improved storage efficiency by retaining only one copy of Git repositories for versioning, preventing excessive disk usage.
Fixed an issue where authentication failures occurred when editing stacks deployed from Git repositories created with version 2.19.0 or 2.19.1.
Fixed an issue introduced in 2.19.0 when deploying from a custom template that was set up via API, where defined mustache variables are not always being prompted for.
Resolved an issue where containers were not deleted when users removed them from asynchronous environments by browsing snapshots.
September 20, 2023
Resolved an issue with snapshots between Edge Agent versions 2.18.2 and Portainer Server 2.19.0, which caused dropping of remote commands in async mode due to mismatches.
Database migration for edge URLs now includes a check to verify if the edge feature is enabled. This fix ensures a more accurate and controlled upgrade process.
Fixed an issue where the migration of Edge Tunnel URLs was broken when the Portainer API URL did not contain a port.
We've improved the transparency of Edge Agent update scheduler and rollback statuses. Now, you'll have clear explanations for each status, simplifying monitoring and management.
We've added a info notice to clarify that the option to update edge agent from a private registry is exclusively available in Edge Agent version 2.18.1 or newer.
Fixed an issue where edge devices in the waiting room were incorrectly counted as part of the dynamic edge group.
Fixed an issue introduced in 2.19.0 where standard and read-only users could no longer view node stats on a Kubernetes cluster.
Fixed an issue introduced in 2.19.0 where the Kubernetes Create Application screen no longer showed in the bottom of page summary when a Deployment would be created.
Fixed an issue introduced in 2.19.0 where MicroK8s cluster creation would fail if the SSH access used a passworded login and sudo access required the password.
Fixed an issue when chatbot integration was enabled globally, where a user who then set a chatbot key could not subsequently clear out their key to turn off the feature for themselves.
Fixed an issue introduced in 2.19.0 when the chatbot integration feature was enabled for a user, where container logs did not display in the log viewer unless in full-screen mode.
Fixed an issue where webhooks were failing when updating a stack deployed from a private Git repository.
We've added a backup reminder for in-app updates, ensuring data safety during the update process.
Resolved issue where failed stack status persists after incorrect compose from Git. Now auto-recovers with the next successful update.
Fixed an issue where usernames and passwords were being stored along with Git stack configurations when Git credentials were used.
Fixed an issue where using spaces in an Organizational Unit (OU) or Common Name (CN) name caused incorrect data to be displayed in the Active Directory configuration.
Fixed an issue introduced in 2.19.0 when Kubernetes environment metrics API features were enabled, where these features would return an 'Unable to reach metrics API' error.
August 31, 2023
Introduced the ability for admins and environment admins to enable/disable community addons on a MicroK8s cluster created via Portainer. Note: On upgrade to this release, existing MicroK8s clusters created via Portainer are set to allow community addons.
A number of components/views have been migrated from Angular to React.
Helm, eksctl, and docker-compose have been updated to newer versions.
Internal versioning on stacks feature has introduced file structure changes in 2.19.
We have addressed an API issue in which an incorrect parameter was being used for API endpoint /edge_groups. Users relying on the HasEdgeGroup parameter should now use HasEdgeJob to achieve the intended functionality.
Resolve identified CVEs.
Updated various packages in the agent, to resolve CVEs.
Fixed an issue where the edge agent was getting disconnected due to user updates to their remote update scheduler.
Resolved an issue where users were unable to create a rollback and subsequently edit it from the scheduler.
Introduced visual enhancement of dynamic progress bar for clearer edge stack status tracking. Get real-time deployment progress at a glance.
Resolved an issue where edge devices were not fully shown in the waiting room when the total amount exceeded 100
Introducing new statuses - 'Running', 'Deploying', and 'Partially running' - for increased transparency in edge stack monitoring.
Introduced staggered deployment & rollback for edge stacks. Update in stages, reduce risks & revert failed updates seamlessly.
Introduced internal versioning & Git commit ID as edge stack version. Clearer version tracking for Git-deployed stacks.
Added support for relative paths in Git-deployed edge stacks.
Resolved an issue where the 'change windows setting' option was shifting outside of the div when a user was using a smaller screen
Fixed an API issue where the incorrect parameter HasEdgeGroup was being used instead of HasEdgeJob for endpoint /edge_groups. Users relying on the HasEdgeGroup parameter should now use HasEdgeJob to achieve the intended functionality.
Introducing the ability to use environment variables for edge stack.
Introducing the latest commit ID display in edge stacks. Perfect for GitOps updates, this feature lets you easily track your running version. Stay informed and up-to-date effortlessly.
Introduced ability to push per-device configurations effortlessly. Bundle settings in a zip package, Portainer matches and delivers to edge devices. Simplify management, enhance precision.
Fixed an issue where the count of edge stack deployments was incorrect when dealing with asynchronous devices exceeding 100.
Fixed an issue where the order of the list changed while logs were being retrieved, and where previously cleared logs were reappearing after retrieving logs for a different environment.
Introduced a feature that empowers you to associate edge devices with newly selected or dynamically generated meta values. Enhance flexibility and precision in device management with this innovative addition.
Introduced an informative enhancement to the waiting room experience. With the addition of the 'Last Check-In' field, users now have valuable insights into when edge devices last communicated with the Portainer server.
Introduced ability to remove edge devices that you no longer want sitting in the waiting room. This feature empowers you with streamlined waiting room management, enabling you to maintain a dynamic and optimised edge environment.
Resolved an issue where editing an existing scheduler caused an error due to a missing edge stack on a related endpoint.
Resolved an issue with Portainer tunnel server address validation error during migration. This fix ensures that when migrating, tunnel server addresses are validated correctly.
Fixed an issue where Edge groups were incorrectly marked as 'in use' after a scheduler was executed.
Addressed an issue where snapshot information was not reliable when the environment was offline. This fix ensures that snapshot information is now accurately presented even when the environment is offline.
Resolved an issue where the count for acknowledged edge stacks was dropping after deployment.
Introduced ability to seamlessly browse snapshots for your asynchronous environment and access detailed stack information.
Resolved an issue around Operator role users not being able to perform rolling restart, redeploy and rollback to previous version for Deployment, DaemonSet and StatefulSet resources.
Resolved an issue introduced in 2.18 that prevented the use of Amazon EKS provisioning of a Kubernetes as a Service (KaaS) cluster.
Fixed a Kubernetes environment issue when restricting access to the default namespace, where any other namespace with a resource quota may have the resource reservations of its apps incorrectly calculated, preventing standard users from editing the apps.
Amended the path for the eksctl binary (used by Amazon EKS KaaS cluster provisioning functionality) to a new expected location.
Resolved an issue on use of the 'Restrict Proc Mount Types' Kubernetes pod security constraint where the restriction was not being applied.
Resolved an issue in the Kubernetes Advanced deployment screen, where a backend panic could occur when deploying some invalid YAML manifests.
Updated the link to Portainer documentation (following docs reorganization) for Kubernetes Add Environment via kubeconfig Import.
Resolved an issue where Node stats for a Google Kubernetes Engine (GKE) cluster gave an error 'unable to retrieve node metrics'.
Introduced the ability to force setting of a note when creating/editing a Kubernetes application (via form), so it can immediately be labelled with its intended use.
Resolved an issue around limiting of Kubernetes pod security constraints updates.
Introduced the ability to set annotations against Kubernetes Services, so they can be configured for service meshes and other tools.
Updated BE Kubernetes Add/Edit Ingress screen to allow use of NodePort or LoadBalancer service types (in addition to existing ClusterIP).
Introduced the ability to specify a manifest to be auto deployed to a Kubernetes cluster when connecting or provisioning one. This allows the environment to be initialized with users, namespaces, secrets, etc., as required.
Introduced showing of the error that occurs when a Kubernetes deployment is prevented by any pod security constraints that have been enabled.
Ensured Kubernetes 1.27 is supported with Google Kubernetes Engine (GKE) provisioning of KaaS clusters.
Ensured Kubernetes 1.26 is supported with Google Kubernetes Engine (GKE) provisioning of KaaS clusters.
Ensured Kubernetes 1.27 is supported with Azure Kubernetes Service (AKS) provisioning of KaaS clusters.
Ensured Kubernetes 1.27 is supported with Digital Ocean Kubernetes (DOKS) provisioning of KaaS clusters.
Ensured Kubernetes 1.26 is supported with Linode Kubernetes Engine (LKE) provisioning of KaaS clusters.
Applied updates and ensured Kubernetes 1.27 is supported with Amazon Elastic Kubernetes Service (EKS) provisioning of KaaS clusters.
Added Beta support for MicroK8s version 1.28 when creating and managing MicroK8s clusters. Note that 1.27 is still the default option for now, as only limited testing of 1.28 has been performed.
Introduced the ability for admins to enable the nfs addon (that has prerequisites) for a MicroK8s cluster, and for admins and environments admins to enable or disable the nfs addon for a MicroK8s cluster, after is has been provisioned.
Introduced the ability for admins to enable the openebs addon (that has prerequisites) for a MicroK8s cluster, and for admins and environments admins to enable or disable the openebs addon for a MicroK8s cluster, after is has been provisioned.
Introduced the ability for admins and environment admins to retrieve a status report on each control plane node of a MicroK8s cluster.
Introduced the ability for admins and environment admins to enable and disable addons that require arguments and generally specify arguments for addons for a MicroK8s cluster.
Introduced the ability for admins and environment admins to connect via SSH console to nodes in a MicroK8s cluster.
Introduced the ability for admins and environment admins to enable/disable community addons on a MicroK8s cluster created via Portainer. Note: On upgrade to this release, existing MicroK8s clusters created via Portainer are set to allow community addons.
Introduced the ability for admins and environment admins to enable or disable addons for a MicroK8s cluster, after it has been provisioned.
Introduced the ability for admins, when removing a MicroK8s environment, to also delete the cluster on the nodes, leaving them in a fresh state, ready to begin again.
Introduced the ability for admins and environment admins to horizontally scale up or down a MicroK8s cluster (i.e. add or remove nodes), after it has been provisioned.
Introduced the ability for admins and environment admins to upgrade the version of a MicroK8s cluster.
Added support for MicroK8s version 1.27 when creating MicroK8s clusters and removed warnings in the UI around a Metrics Server issue with MicroK8s 1.25 and 1.26, now that they've been patched to resolve the issue.
Fixed an issue in Environment and Cluster Details screens for a MicroK8s cluster that failed to provision via Portainer. In this scenario, the display of enabled addons no longer triggers (whereas, it would previously still attempt it, causing a problem).
Added info text to Kubernetes MicroK8s functionality to inform that nodes must be internet routable and open on certain ports.
Added a link to the Portainer Assistant/Chatbot settings taking you to an explanatory blogpost.
Fixed an issue where the Portainer Assistant/Chatbot icon could eclipse list table screens' pagination.
Introducing a new feature that enhances version tracking and clarity for stacks deployed from Git repositories.
Resolved an issue around orphaned environments being included in the total count of nodes.
Fixed an issue where saving Git credentials and subsequently redeploying a stack resulted in an error.
Fixed an issue where edge devices were incorrectly counted as nodes while in the waiting room. Now, waiting room devices are excluded from node count, ensuring accurate resource allocation and adherence to policy.
Fixed an issue where using spaces in an Organizational Unit (OU) or Common Name (CN) name caused incorrect data to be displayed in the Active Directory configuration.
Fixed an issue where Git deployment did not synchronize authentication status.
Provided icons for 'image up to date' indicators (in place of the previous colored circles) shown in Docker Stacks, Services and Containers list screens. This improves accessibility for color-blind users.
Resolved an issue where users were unable to browse image tags in a private Sonatype registry.
Resolved an issue where mouse clicks were not functioning within the "Display Users" section of Active Directory under authentication settings.
Resolved a minor grammatical issue with a log line recorded when the Docker image up to date indicator check runs but there are no registries defined.
Added a feature that allows users to update to the latest Portainer Business Edition version directly from within the app
Improved the way ANSI escape codes are handled in logs. With this enhancement, logs will now provide clearer and more readable information by effectively stripping out ANSI escape codes.
Corrected API method from 'GET' to 'POST' and path for generate edge key in Swagger API docs
Corrected an error in our Swagger API documentation where 'EdgeTunnelServerAddress' was marked as required. It is now correctly marked as optional
Removed the incorrect documentation for the DELETE method on the license API, as it is not supported. Documented the correct way to perform the operation using the POST method on the license API in Swagger API documentation.
July 7, 2023
Fixed issue where registry credential does not sync between registry configuration page and registry details page.
Fixed an issue around prompting for a new license.
Improved the way node count shows for trial licenses.
Resolved an issue where update or rollback was only executed when connection was re-established.
Introduced a change to allow removal of all Portainer licenses.
Fixed an issue where a warning banner was not always showing in the Homepage or Licenses page when licenses were close to expiring.
Corrected 'container' to 'containers' in Swagger API docs (Business Edition).
May 22, 2023
In this release, we introduce an experimental ChatGPT integration. Although it promises exciting possibilities, it's in the early stages of development. We recommend its use for testing and development, and urge caution in production environments. We greatly appreciate your feedback and understanding during this phase.
Fixed issue preventing configuration of Portainer authentication settings with an alternative mTLS certificate
Resolved issue causing edge agent to skip command processing during full snapshot resend
Introduced ChatGPT integration as an experimental feature, currently not recommended for production environment use
May 1, 2023
Users upgrading from 2.16.x should note that a bug was introduced then which prevented enforcing of TLS verifications. This has now been fixed but, in circumstances where certificates were not set up correctly and appeared to work due to the bug, you may now need to resolve the certificate issue or deliberately set the new ‘Skip verification’ toggle.
Fixed issue where users were unable to update their Edge Agent to the latest version because the corresponding option was not available when creating a scheduled update
Fixed issue where the port number in the displayed webhook link was incorrect when Portainer was running behind a reverse proxy
April 18, 2023
Please note 2.18.0 is not publicly available. This release is 2.18.1 and is our next GA release since "2.17.x". This was done due to the need to provide an upgradeable preview image to a customer.
The Kompose functionality in Kubernetes has been removed since 2.17.0. Compose yaml can no longer be deployed on Kubernetes.
Moved edge devices to the homepage view and removed edge devices menu option under edge compute.
Add devices button is replaced with new UX in environment wizard.
Since release 2.17.x we have added the ability to upgrade Edge Agents from Portainer when running on Docker Standalone / Docker Swarm / Nomad. Before using this feature we strongly advise to test this on a non-production environment first and have an alternative method available to connect to the Edge Device.
Any clusters connected to Portainer of version 1.23 Kubernetes and above will have their Pod Security Policies (if they have any and are using the pod security constraints feature) updated to the Pod Security Standards
Introduced a retry policy for edge stack deployment to improve success rate
Fixed issue where browse snapshot button was clickable for Kubernetes and Nomad edge agents in async mode
Fixed issue where upgrading edge agent from ECR private registry using certificates failed
Fixed issue when browsing async edge agents before first snapshot is received.
Fixed issue when browsing non-existent async agent snapshot cause backend panic
Fixed issue for remote update schedules error incorrectly displaying for non admin users
Fixed the issue where the edge stack is not removed from edge agent when it has been deleted while edge agent is offline
Fixed issue where edge agent panics with malformed edge key
Introduced ability to view container's environment variable when browsing snapshot
Introduced remote updating edge agent from a private registry for docker standalone environment
Introduced ability to assign group, edge groups and tags to edge environment when using AEEC script
Fixed issue where edge job logs was not retrieved correctly when edge groups contain async devices
Changed default value for async check-in intervals from disabled to 1 minute to improve success rate of initial edge agent connection
Renamed AEEC to "Auto onboarding" for better user understanding
Introduced a new feature to allow creating of a MicroK8s Kubernetes cluster on existing machines.
Fixed an issue when provisioning a Civo Kubernetes cluster with the Kubernetes version left as the latest, due to Civo introducing Talos as a new Kubernetes cluster type (instead of K3s on Alpine) which then only applied to the latest Kubernetes version.
Introduced the ability to set annotations against various different Kubernetes objects via the existing form pages.
Introduced the ability to upload an internal SSL/TLS certificate which can then be used to access a Helm repository hosted on a private server.
Updated the pod security constraints feature to use newer OPA Gatekeeper 2.9 and moved the feature away from using Pod Security Policy resources with Kubernetes clusters of 1.23 and above (as they are now removed in Kubernetes 1.25 and above).
Added migration to ensure existing pod security constraints work on environments with new Pod Security Standards of updated OPA Gatekeeper 2.9. This includes migrating edge environments on post-upgrade connect that may occur on clicking into via Homepage.
Resolved an issue where pod security constraints were not being enforced (since 2.16).
Fixed issue where users are not able to re-create container with multiple networks
Fixed issue with relative path not working when private registry is used, due to private registry credentials not passing to unpacker
Defaulted the image up to date indicator to on for new Docker environments added, or on upgrade from CE to BE for all Docker environments (now that caching and Ajax load performance improvements have been applied to this feature).
Fixed issue where Nomad Edge Agent install script causes error when using environment variables
Introduced ability to upgrade edge agent in Nomad environment from within portainer UI
Fixed issue where container log not showing when logs contain NULL value
Added form validation for S3 compatible host field
Fixed issue where stack can not be deleted if relative path is removed from the mount point
Fixed issue where you can not connect or configure Azure private registry from Portainer while registry is empty
Added release testing of ARM32 architecture for Portainer Agent
Updated hide internal authentication prompt option to default to off
Introduced ability to use different certificate for mTLS communication between Portainer server and agent.
Resolved a minor issue in the Browse Registry screen on Kubernetes environments, where the Registries breadcrumb link would take non-admin users back to the Homepage instead of the Registries list screen.
February 22, 2023
Fixed an issue where Edge Agent updater leaves behind limited stack.
Fixed an issue where node enforcement message displayed incorrectly for trial license users.
Fixed an issue where git credentials are not selected when editing stack deployed from git repository.
February 7, 2023
Running Portainer with Docker Engine <= 19.03 (Docker API <= 1.40) will cause a fatal error similar to failed initializing upgrade service | error="failed to determine container platform: failed to retrieve docker info: Error response from daemon: client version 1.41 is too new. Maximum supported API version is 1.40"
The Kompose functionality in Kubernetes has been removed. Compose yaml can no longer be deployed on Kubernetes.
Moved Edge Devices to the homepage view and removed Edge Devices menu option under Edge Compute
Add devices button is temporarily located on the Edge Compute Settings page
This release has added the ability to upgrade Edge Agents from Portainer when running on Docker Standalone. Before using this feature we strongly advise to test this on a non-production environment first and have an alternative method available to connect to the Edge Device.
Introduced the ability to remotely update edge agents from within Portainer
Introduced option for pre-pull of images for edge stack deployment to increase deployment success rate
Added edge group support in edge jobs to allow execution across many devices
Introduce the ability to edit edge agent tunnel URL and API server URL from within Portainer
Clarified UX around polling intervals and poll frequency option in edge compute settings between async and normal edge agents.
Added info text to waiting room view
Fixed issue where edge stack failed to deploy with private registry in async mode
Fixed issue where actions icon under edit edge stack page is not consistent
Introduced new log viewer to Portainer Business Edition
Introduced the ability to edit the YAML manifest of Kubernetes objects and apply the changes via the Kubernetes patch function
Introduced global and cluster-level options to allow enforcing of code-based deployment of Kubernetes objects, preventing the use of Portainer forms and other less easy-to-repeat workflows
Introduced a new setting in the Cluster setup screen of a Kubernetes environment to allow enforcing of admin-only deploying of ingresses
Introduced the ability to specify updates to existing environment variables of a deployment via query string parameters on the Kubernetes application redeploy webhook
Added a rolling restart button to the Kube application UI
Introduced a new rollout-restart parameter to Kube application redeploy webhooks to allow remote initiating of zero-downtime deployment rolling restarts
Introduced an alternate means of authenticating connections to the Google Cloud platform (used by our KaaS provisioning of Google Kubernetes Engine environments), following their deprecation of the gcp auth plugin in Kubernetes v1.22 and removal in v1.26
Introduced experimental Kubernetes functionality (behind a feature flag) to allow installing of MicroK8s to existing machines
Updated Kubernetes as a Service (KaaS) cluster provisioning to use the latest eksctl tool for the AWS EKS platform, and support up to v1.23 of Kubernetes (use of this version was previously failing)
The Kubernetes Operator role is not intended to have secrets update permission and hence, as a security consideration, this permission is now removed from Portainer
Resolved an issue that was causing an 'Unable to get k8s environment access' error on deleting of a Kubernetes edge environment
When connecting a Kubernetes environment to Portainer via kubeconfig import, stop deleting of any extant 'portainer' namespace in the cluster
When using Kubernetes (KaaS) cluster provisioning and choosing the Azure Kubernetes Service (AKS) option, only node size options that are valid for provisioning now show. Previously, there was at least one option which gave an error on use
Resolved two scenarios where importing of the kubeconfig of a Kubernetes cluster raised an error that caused a stuck 'Deploying' status
In Kube Create namespace and Namespace details screens, made the resource assignment toggle always visible - even when the cluster's resource over-commit option is off (when it will show but be disabled for change)
Fixed an issue introduced in 2.16 where the Kube Create namespace screen's CPU and Memory resource allocation max limits did not have other namespaces' resource amounts subtracted when the cluster's allow resource over-commit option was turned off
Introduced new log viewer to Portainer Business Edition
Introduced pull image param for stack webhook to turn pull-image on and off
Introduced 24 hour caching for new image notification
Fixed issue where container webhook URL always changed on each recreation
Introduced support for GitHub container registry as a registry type
Updated Portainer dependencies of Business Edition
Fixed issue where admin users are not able to delete expired or revoked license
Fixed issue where user is not removed from team when removed from LDAP group
Fixed issue around task logs not loading if they are empty
Fixed issue where old UI components were still being used for Nomad related pages
Replaced aws-sdk-go with aws-sdk-go-v2
(swagger) fix licenses attach route
GET /docker/{environmentId}/containers/{containerID}/image_status
GET /docker/{environmentId}/services/{serviceID}/image_status
GET /docker/{environmentId}/stacks/{id}/images_status
GET /kubernetes/{id}/namespaces/{namespace}/applications
GET /kubernetes/{id}/namespaces/{namespace}/applications/{kind}/{name}
GET /kubernetes/{id}/rbac_enabled
GET /nomad/endpoints/{endpointID}/leader
GET /system/info
GET /system/nodes
GET /system/status
POST /system/upgrade
GET /system/version
PUT /webhooks/{id}/reassign
GET /nomad/endpoints/{endpointID}/status
GET /status - Deprecated: use the /system/status endpoint instead to retrieve the Portainer status.
GET /status/nodes - Deprecated: use the /system/nodes endpoint instead.
GET /status/version - Deprecated: use the /system/version endpoint instead to check if portainer has an update available.
POST /backup/s3/execute
POST /backup/s3/restore
POST /backup/s3/settings
POST /edge_jobs
POST /edge_jobs/{id}
POST /edge_stacks
PUT /edge_stacks/{id}
POST /edge_update_schedules
GET /edge_update_schedules/active
PUT /endpoints/{id}
PUT /endpoints/{id}/settings
POST /registries
PUT /registries/{id}
PUT /settings
POST /stacks
November 21, 2022
November 9, 2022
Fixed an issue with view/edit of an external application (i.e. one originally added to the cluster outside of Portainer) where a 'cannot read properties' error was shown.
Fixed an issue with view/edit of Kubernetes namespaces where memory and CPU resource limit sliders were positioned incorrectly and erroneous warnings were shown.
Fixed issue of update stack button being disabled when updating an existing stack.
Fixed license key issue where node counts were not updated when environments are deleted.
Fixed issue with JSON formatted logs failing in 2.16.0.
October 31, 2022
Proposing to deprecate ACI (Azure Container Instances) and remove the functionality to connect to ACI, view existing containers and deploy new containers.
portainer/portainer:latest moved to portainer/portainer:2.16.
Migrated from Angular to React: Tag selector for Environment Details view.
Migrated from Angular to React: Teams view.
When upgrading to 2.16, if you already have ingress controllers in a Kubernetes cluster/environment linked to Portainer and used Portainer to set them at the cluster and namespace level, and if these ingress controllers were not used by any ingresses, after the upgrade, you may end up with dummy ingresses visible in the new Ingresses screen in Portainer (that are not actually used for any deployment). This is simply an artifact of how we retained information about ingress controllers in earlier Portainer releases. If you find these kinds of dummy ingresses, you can safely delete them.
The Homepage's kubeconfig download dialog now only includes those environments that show on the Homepage. Those with a connection error or provisioning error (these states were introduced in recent releases) are now excluded.
Fixed issue with deploying custom templates on Kubernetes that are using mustache variables.
Set notification of new image for docker default to off.
Resolved an issue in Docker Services, Containers, and Stacks, where loading of the recently added out-of-date image indicator delayed showing of a row's action icons.
Fixed the issue where the container webhook toggle was not being saved.
Fixed an issue where a console error was showing for GPU when using Swarm because GPU is not supported on Swarm.
Fixed an issue where the image pull limits weren't being shown for standard users.
Introduced the offering of auto-suggestions retrieved from the git repo when entering the Compose path.
Added the ability to store git credentials in user settings.
Introduced login screen banner to the login page.
Added banner for "new version available" in portainer business edition.
Update golang and image dependencies for API and portainer binary ( EE ).
Fixed an issue where the Microsoft OAuth information was not being retrieved correctly when editing the settings.
Fixed select all behavior in environments page.
Fixed the issue of handling images built by buildx or buildkit in the registry browser.
Fixed issue with text color and text background color on auto-filled text.
Introduced UI info components while browsing snapshots.
Introduced the ability to run remote commands on edge environments connected via Async using mTLS.
Introduced UI info components while browsing snapshots.
Fixed issue around Home page loading time when you have Nomad environments connected.
September 16, 2022
September 6, 2022
Breaking change in API where the endpoint filter edgeDeviceFilter has been replaced by edgeDevice and edgeDeviceUntrusted.
Migrated docker/containers/list views to React.
Migrated the Docker console.
Migrated Azure Container Instances views to React.
Migrated the sidebar menu and adjusted the Settings page.
Migrated the Kubectl shell window.
Migrated tooltip into react component.
Migrated page header into React component.
Introduced the ability to define pod security constraints per Kubernetes cluster.
Resolved some errors and wording issues in recent KaaS cluster provisioning and import kubeconfig functionality.
When using Kubernetes (KaaS) cluster provisioning and choosing the DigitalOcean option, only node size options that are valid for provisioning now show. Previously, there was at least one option which gave an 'invalid droplet size' error on use.
Introduced the ability to disable use of the anonymous Docker Hub registry option via the Portainer UI for all users.
Introduced support for checking images held in private registries to the recently added functionality that shows a visual image indication on stacks, services and containers that are running with an out-of-date image.
Introduced license enforcement for 5 nodes free in business edition.
Added tips for entering Portainer license key.
Fixed issue where Automatic team membership did not always work for Azure.
Fixed an issue where auto populate team admins LDAP feature didn't work on upgrade from CE to BE.
Fixed license expiry message flashing even license is not expired or close to expiring.
Reworded error message for JWT token missing to more user-friendly message.
Introduced the ability to get logs for edge stacks of specific environments.
Fixed connection issue ("Environment is unreachable") after deploying Nomad environment with AEEC script.
Fixed known issue with manually adding an Edge Device environment through the edge device page when using Async mode, does not retain Async settings and needs to be manually added through the environment details page.
Improved image parsing for Kubernetes Edge Stacks that use private registries so that the same parsing as Docker ones is used.
Standardized the behavior of Nomad edge environments to be the same as non-Nomad edge environments.
July 26, 2022
Known issue with manually adding an Edge Device environment through the Edge Device page when using Async mode, does not retain Async settings and needs to be manually added through the environment details page.
Image update notifications are currently not supported for private registries and private images in DockerHub. This is due to be fixed in our next major version.
Fixed an issue when using a Mustache variable (e.g. {{service}}) multiple times in the YAML, where the UI should prompt for it only once and then reuse it (rather than prompting for it multiple times).
Fixed an issue when using a Mustache variable (e.g. {{path}}) with special characters in the value, where the resulting value would end up being HTML encoded.
Fixed issue around access control labels being ignored.
Fixed an issue where auto populate team admins LDAP feature didn't work on upgrade from CE to BE.
Resolved an issue where new installs of recent Portainer releases had an extraneous (although innocuous) db version update on restart.
July 12, 2022
Known issue with manually adding an Edge Device environment through the Edge Device page when using Async mode, does not retain Async settings and needs to be manually added through the environment details page.
Image update notifications are currently not supported for private registries and private images in DockerHub. This is due to be fixed in our next major version.
When using a Mustache variable (e.g. {{ service }}) multiple times in the YAML, the UI also prompts for it multiple times, rather than prompting for it a single time and then reusing it.
Improved KaaS cluster provisioning's cluster name validation to enforce restrictions that Google GKE expects.
Fixed issue of variable inputs not showing on deployment view when using custom templates.
Improved Portainer logging to better record the output from eksctl, the CLI tool used for Amazon EKS (KaaS) cluster provisioning.
Fixed an issue where, upon initiating AWS KaaS cluster/environment provisioning and subsequently restarting Portainer in a short space of time, the requested environment would become stuck and unusable in Portainer, and couldn't be deleted.
Fix to improve LDAP, etc. authentication/login speed when there are many thousands of users.
June 28, 2022
Known issue with manually adding an Edge Device environment through the Edge Device page when using Async mode, does not retain Async settings and needs to be manually added through the environment details page.
Image update notifications are currently not supported for private registries and private images in DockerHub. This is due to be fixed in our next major version.
With the upgrade to Docker Compose V2, container names now use hyphens as separators instead of underscores. This may affect you if you are generating container names instead of explicitly defining them, then using them as references.
Introduced ability to set up a new Kubernetes environment in Portainer via upload of a kubeconfig file for an existing on premises or on-cloud cluster.
Administrators can now set up cloud provider settings via a list page and separate add page in a similar way to other records in Portainer.
Introduced support for provisioning of a Kubernetes cluster on the Amazon (AWS) EKS platform from within Portainer, alleviating the need to do so in the cloud provider's portal. The AWS eksctl binary is auto downloaded when first using this functionality.
Introduced support for provisioning of a Kubernetes cluster on the Microsoft Azure AKS platform from within Portainer, alleviating the need to do so in the cloud provider's portal.
Introduced support for provisioning of a Kubernetes cluster on the Google Cloud GKE platform from within Portainer, alleviating the need to do so in the cloud provider's portal.
Fixed an issue with cluster provisioning via Civo KaaS, where if the Civo account has an issue with its defined networks, the environment was stuck waiting to complete provisioning and never ultimately errored.
Introduced the ability to set the group and tags against the environment in Portainer when an admin provisions a Kubernetes as a Service cluster.
Introduced slight improvements to editing of sensitive cloud credentials values.
Fixed an issue in the Settings -> Environments page, where an environment that was disabled or still being provisioned could be selected for removal and then removed.
Added the ability to manually refresh pulling of Kubernetes as a Service cluster provisioning options from cloud providers.
Improved error handling around KaaS provisioning in the environment wizard.
Kubernetes as a Service (cloud) provisioned environments will now appear in the 'new environments' side panel in the environments wizard.
Introduced ability to pass environment variables on the webhooks in Docker stack deployment.
Third-party developer Inedo has fixed their ProGet registry software to resolve an intermittent error admins were experiencing in Portainer on retag or delete of a tagged image. This is planned to ship 10 June 2022 in ProGet 6.0.16, before Portainer 2.14.
Introduced support in the container webhook for pull/recreate of containers from images residing in private registries.
Fixed an issue in the Containers page, where choosing 'Recreate' enabled the webhook for the container, even though it was not currently turned on.
Introduced support for provisioning of a Kubernetes cluster on the Amazon (AWS) EKS platform from within Portainer, alleviating the need to do so in the cloud provider's portal. The AWS eksctl binary is auto downloaded when first using this functionality.
Introduced support for provisioning of a Kubernetes cluster on the Microsoft Azure AKS platform from within Portainer, alleviating the need to do so in the cloud provider's portal.
Introduced support for provisioning of a Kubernetes cluster on the Google Cloud GKE platform from within Portainer, alleviating the need to do so in the cloud provider's portal.
Fixed an issue recently introduced in the environments page where the name of an environment that was down no longer linked through to its details page.
Resolved an issue preventing migration from EE 2.12 to 2.13 (or now 2.14) for Portainer instances that had previously migrated to EE from a CE instance with Allow Volume Browser for Regular Users toggled on for an environment.
Fixed propagation of Portainer agent polling frequency when changed before deploying via automatic edge environment creation
Introduced the ability to paste in an existing license, revalidate with the license server and replace it in the database. This can be used to fix a corrupted license.
Introduced the ability to define the 3 polling intervals for Async
Added HTTPS support for Nomad Edge Agent.
May 12, 2022
May 9. 2022
When provisioning a Civo cluster while there are multiple default networks defined on the Civo account, the environment will fail to provision and Portainer will end up waiting for the environment to be ready indefinitely. This can be resolved from the Civo console by deleting the cluster and using a non-default network for the provision.
The minimum TLS version of Portainer was changed from 1.2 to 1.3. If you are running a proxy in front of Portainer with HTTPS you will need to ensure it is configured to support TLS 1.3.
Standard users can browse registries including edit and delete
Introduced the ability for non admin users to browse image registries
Added strong password policy for all Portainer internal users. When using a weak password and logging in you will be required to update your password.
Introduce support for provisioning of a Kubernetes cluster on a cloud provider's KaaS offering from within Portainer, alleviating the need to do so in the provider's own portal. Initial supported providers are Civo, DigitalOcean and Linode.
Fixed issue where changing Portainer to HTTPS crashed Portainer: portainer/portainer#6836
Standard users can browse registries including edit and delete
Introduced the ability for non admin users to browse image registries
Fixed issue where upgrading to the Business Edition and then downgrading back to the Community Edition did not work
Improved file type validation when selecting multiple files when deploying from Git repository
Removed superfluous warning message for the Enable Change Window setting
Fixed text color for change window warning text
Renamed Trust on first connect to "Waiting Room"
Introduced the ability to pass env variables from local system to edge stacks for Kubernetes environments
Created the ability for Automatic Edge Environment Creation (AEEC) within Portainer Server
Introduced support for using credentials with private registries for edge stacks
April 4, 2022
Introduced Nomad integration
Allows Nomad to be added as an environment in Portainer by using the Edge Agent
Allows Edge Stacks to be deployed on Nomad as Nomad Jobs
Allows Nomad Jobs and Tasks to be listed
Allows Nomad logs and events to be viewed for Tasks
Fixed issue where changing Portainer to HTTPS crashed Portainer
Fixed issue around deploying in default namespace via manifest using the portainer namespace instead
Fixed bug causing domain names to not displaying correctly under publish application options
Fixed issue with first service naming having a suffix attached.
Improved error message being displayed when deploying a malformed Kubernetes manifest from GitOps
Fixed issue with GitOps automatic update
Fixed issues around migration path for CE to BE
Fixed missing operator role when migrating from 1.x
Resolved some race conditions with the Edge Agent
March 9, 2022
Fixed bug where redeploying a stack causes an error and success message at the same time.
Fixed bug that was preventing ability to edit application with persisted folder on Kubernetes.
March 8, 2022
Deploying a manifest without a namespace definition and selecting the Default namespace in Portainer may deploy the application into the portainer namespace in certain circumstances
Fixed issue with displaying container template when connected to docker swarm in the app templates page view
Fixed issue where upgrading from CE to BE failed due to missing RBAC roles
Standard users will no longer be able to remove or export images. Also, Operators, Help Desk, and ready only users will no longer be able to export images.
Fixed issue with default helm repo not populating in settings page
Introduce the ability to pass env variables from a local system on edge devices to the edge stack
Fixed minor UI behavior with toggles in Edge Compute settings view
Fixed issue with displaying AMT device table for non-activated devices
Fixed minor UI issues in Edge devices page view around Action buttons
November 15, 2021
Access can not be assigned to registries when defining multiple registries with the same URL
Browser cache causes UI abnormalities after upgrading from a prior version. Force a cache refresh (Ctrl-Shift-R) to remedy
As a consequence the --ssl flag has been deprecated. If you are using the --sslcert and --sslkey flags, then after the upgrade port 9000 will serve http and port 9443 will serve https with the provided certificate. To retain the old behavior consider using the port mapping -p 9000:9443 instead.
Introduced the ability to keep the deployments of stacks and applications in sync with the definitions in Git
Fixed issue where Environment variables with empty values are not showing when editing a Kubernetes application
Fixed issue where standard users could not see the quota set in the namespace details page
Introduced the ability to keep the deployments of stacks and applications in sync with the definitions in Git
Fixed issue where switching from docker standalone to swarm would show duplicate stacks
Added automatic updates of stacks and applications to the activity logs
Introduced the ability to define a time based change window in which automatic updates of stacks and applications can take place
Introduced the ability to automatically set OAuth users as a Portainer Admin
Introduced the ability to automatically set LDAP users as a Portainer Admin
Added a Portainer and Agent Juju Charm to the Charmhub marketplace
Fixed issue where RBAC settings would be retained after removing an Environment from Portainer
Fixed issue where certificates would end up in the activity logs
Fixed issue when exporting activity logs as CSV without a data range set
July 29, 2021
Added the ability to update and redeploy a stack created from a git repository
Added I/O usage to the container statistics
Enhanced environment variables UI/UX for Docker
sysctl options are available when creating a container
Show the number of Swarm nodes for the endpoint on the Home page
Show how many Docker pulls are remaining for DockerHub to avoid exceeding the quota
Introduced support for compose version 3.8 on docker swarm environments
Display the container IP address(es) in the list of containers
Improved layout of the toggles on the create container setting tab
For Docker Standalone, prevent a stack from being created if the Compose has a container_name that already exists
Creating a container from a DockerHub image will show a search button in the UI
Fixed issue where deploying a stack from Git did not work for Azure DevOps
Fixed issue where stacks with a status of 0 are hidden in the UI
Fixed issue where pulling a large image is failing when using an Agent due to a timeout
Fixed issue where listing the services with Auto-refresh on collapses all services after refresh
Fixed issue where dash characters got removed from the stack name on Docker Standalone
Fixed issue where access control management via labels was not fault tolerant
Fixed issue where the label showing the default location of secrets was incorrect for Windows
Fixed typo in the error message "Unable to start stack"
Added ProGet as a specific registry type when adding a registry
Fixed issue where pushing to a quay.io registry failed due to not including the username in the quay registry URL
Fixed issue where creating a custom template from uploading a compose file failed
Fixed issue where switching custom template in the template tab of stack create view doesn't update editor
Fixed issue with an invalid template documentation URL in the Settings
Added validation to prevent adding empty mount to an existing service
Fixed issue with the MountType and nfsvers when creating NFS4 volumes
Fixed issue where editing the properties of volumes on a service did not enable the apply button
Introduced the ability to deploy a manifest from a git repository when using advanced deployment
The advanced deployment feature has been made available to standard users
Introduced a summary of Kubernetes actions when deploying a Kubernetes resource
Added the ability to display realtime node metrics in Kubernetes
Added functionality to allow multiple ingress networks per kubernetes namespace, with a differing config per ingress
Added the ability to redeploy an externally deployed application
Added the ability to expand the YAML tab of a Kubernetes application to full size
Added the ability to cordon/uncordon/drain nodes
Added a warning in the placement tab when an application can't be scheduled on the cluster
Renamed Resource Pools to Namespaces in the UI
Improved UI for the placement policies when creating an application
Improved how application image names are shown
Form validation has been added for Configuration keys
Environment variable are sorted alphabetically to improve the readability
Display the ImagePull policy in the details of an application
Default to the kube-system namespace in the advanced deployment view on ARM
Fixed minor UI inconsistency when creating an application with an ingress
Fixed issue with the UI layout when creating an application with ingress
Fixed issue where updating the Kubernetes endpoint URL did not get persisted
Fixed issue where the endpoint url is not updated when updating a kubernetes local endpoint
Fixed issue where renaming the endpoint of a kubernetes agent breaks the endpoint
Fixed issue where environment variables with empty values are not showing when editing a kubernetes application
Fixed issue where environment variable validation when creating an application was too restrictive
Fixed issue where creating an application with two different ingresses incorrectly populates the hostname UI fields
Fixed issue where an application with persisted data can't update, after the storage option is disabled in the cluster settings
Fixed issue where adding an ingress route is not prevented when editing an application with existing ingress route and ingress is disabled
Fixed issue where adding an application does not allow Global to be set
Fixed issue where ACI stops working after persistence or networking gets added
Added the ability to deploy Edge stacks on Docker standalone Edge endpoints
Show the status of the edge agent check-in on the home page dashboard
Hide the webhook UI in the service creation view of an edge endpoint, since it's not applicable
Fixed issue where accessing a down Kubernetes Edge endpoint should redirect the user to the home view
Added the ability to sync Portainer teams with group memberships provided via OAuth
Added SSO support for OAuth and do not enforce a login prompt. Use <portainer_url>/#!/internal-auth to login with internal admin.
Added the ability to manage orphaned stacks when Portainer has the compose file
Added the option to specify the local socket location when adding a docker endpoint
Search filters are retained within the browser session
Properly expose backend error when using image management features
Prevent web editor related views from being accidentally closed
Improved descriptions for Portainer initialization errors
Disable sysctl settings for non-administrators incorrectly defaults to being on
Fixed issue where the File select windows gets shown when pressing enter in text fields
Fixed issue where restoring Portainer from a backup file fails in certain circumstances related to the activity logs
Fixed issue where a custom snapshot interval cannot be changed
Fixed issue with incorrect Windows agent deployment command in the agent endpoint creation tab
Introduced initial experimental support for Podman. Known limitations are listed in https://github.com/portainer/portainer/issues/5188
Introduce buildx to support Windows 1903+ Base Images
Added the ability to debug through VSCode
Added check for missing angularJS inject annotation
Removed grunt-karma ang grunt-html2js dependencies
Fixed issue where webpack complains about charset source maps
Fixed issue where babel complains about missing core-js dependency
Logging into Portainer as a Standard User fails to load home page when using 'microk8s v1.21.3-3+6343a564e351b0'
Host Browser function does not work for Non-Admin users.
May 4, 2021
Pods without workloads are now displayed as applications
Improved UI/UX of configurations for creation / edition
Introduced request of confirmation upon volume removal
Introduced the advanced deployment panel to each resource list view
Updated validation to prevent a user from exposing an application over an external load balancer with mixed protocols
Introduced the ability to display the access policy associated to the storage of a volume
Clarified advanced deployment feature
Clarified sensitive configuration creation
Clarified ingress controller configuration in the cluster setup view
Renamed the create entry from file button when creating a configuration
Improved validation warnings in the application creation / edition views
Removed extra whitespace in stacks and storage datatables
Fixed issue with access management feature on resource pools
Fixed issue with ability to retrieve configs when a config is a binary file
Fixed issue with advanced deployment feature on agent and Edge agent endpoints
Fixed an issue that would mark a sensitive configuration as external without owner after an update
Fixed issue with access to configuration details view for a configuration containing binary data
Fixed labels to display system labels first in the node details view
Fixed refresh issue on the view with the YAML panel selected
Fixed invalid display issue when accessing the load balancer panel from the application panel
Fixed issue when accessing the cluster setup incorrectly expanding the Endpoint sidebar
Fixed issue with exposed configuration keys over filesystem inside an application not being applied
Fixed issue when Adding a key to existing used configuration that would throw an error when editing an application using that configuration
Fixed an issue with the form validation in the configuration creation view
Fixed issue with resource pool “created” attribute not showing actual creation time
Fixed issue with ability to apply a note to a Pod type application
Fixed issue with creating Kubernetes resources with a username longer than 63 characters
Fixed issue with special characters in usernames when creating Kubernetes resources
Fixed issue with ability to retrieve config map error when trying to manager newly create resource pool
Introduced user authentication activity logging
Introduced user activity logging
Introduced new RBAC “Operator” Role
Fixed issue with user in 2 team with mix of helpdesk & endpoint admin resulting in the user having permissions of endpoint admin
Fixed issue causing Portainer to forget the password associated to a registry after an update
Fixed issue preventing the registry manager feature to work properly with a ProGet registry
Improved description for advanced mode usage with private registries
Introduced validation to prevent adding a mount with nothing filled to and exiting service
Fixed issue in service creation, switching to bind mode from volume mode with a volume selected fills the host field with {object Object}
Introduced support for creating stacks with the same name across different endpoints
Introduced extra stack information: creation, last update time and user who created the stack
Minor UX change for the start/stop stack action
Fixed issue with ability to use private registries with Standalone stacks
Fixed issue showing editor tab on limited stacks when it should not
Fixed issue when editing a stack, hitting backspace or delete keys with contents of web editor selected hides the entire editor UI element
Fixed issue with stack create via API with a regular user account are incorrectly marked as administrator only
Fixed issue of error being displayed when creating a stack on docker standalone despite the stack is created
Fixed issue of stacks being created via API incorrectly marked private with no owner
Introduced support for Compose > v2 when deploying a stack on a Docker standalone environment
Introduced the ability to download log file from Docker container/service views
Display labels in Image Details
Clarify the description of the restrict external access to the network property when creating a network
Automatically lowercase username when authenticating users
Update the authentication UX to put an emphasis on OAuth when OAuth is enabled
Introduced the ability to backup / restore Portainer
Fixed issue of version not being shown correctly after update
Support starting Portainer without having to specify any endpoint
Introduced RBAC to ACI
Introduced UAC to ACI
Removed the new version check
Changed the license server errors to be a silent fail for offline environments
Added JS source map for Portainer UI
February 22, 2021
Fix an issue preventing a user from creating Kubernetes resources if they have a @ character in their username
Users with a @ character in their username were not able to create the following Kubernetes resources:
Resource pool
Application
Configuration
Fix platform issues with the Docker image for Portainer Business The Docker image can now be successfully deployed on the following platforms:
Linux ARM64
Linux ARM
Minor update to the license server mechanism The license server mechanism has been updated.
December 3, 2020
Initial release of Portainer Business
This is a STS (Short Term Support) release that includes all the changes added up to and including the 2.25.1 patch release as well as various fixes aimed at enhancing the stability and scalability of Portainer. For more details on what is included from the 2.25 release, refer to the .
CVE-2024-45337 []
Fixed an issue where excessive warnings were logged if agents weren’t updated to match server version []
This is a that includes all the changes added up to and including the 2.24.1 patch release as well as various fixes aimed at enhancing the stability and scalability of Portainer. For more details on what is included from the 2.24 release, refer to the .
This is a that includes all the changes added up to the 2.23 release and 2.21.4 LTS patch release, as well as various fixes aimed at enhancing the stability and scalability of Portainer. For more details on what is included from the 2.23 release, refer to the .
This is a that includes all the changes added up to and including the 2.22.0 release, as well as various fixes aimed at enhancing the stability and scalability of Portainer. For more details on what is included from the 2.22 release, refer to the .
This is a that includes all the changes added up to and including the 2.21.2 release, as well as various fixes aimed at enhancing the stability and scalability of Portainer. For more details on what is included from the 2.21 release, refer to the .
For detailed information about the changes included in the 2.20.x releases, please refer to the .
This is an STS (Short-Term Support) release. Read more in our .
Resolved an issue introduced in 2.20.0 where stopped Docker containers were incorrectly shown with an Unused badge.
Resolved an issue where the Edit Container page on Swarm environments was not loading properly.
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.
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.
Introduced a tooltip to the 'Rollback to previous configuration' button in the Kubernetes Application Details screen to explain how rollback works.
Prevented a panic from occurring when mistakenly attempting to deploy a Kubernetes application and supplying a docker-compose.yaml instead of a Kubernetes manifest.
Resolved an issue where pending actions to be run on environments could end up in a panic state.
Resolved an issue where the subpath of an image tag was incorrectly truncated.
Resolved an issue around excessive GitHub API Portainer version checking on page loads.
Resolved an issue where loading a large number of volumes took an unreasonable amount of time
Resolved an issue in the agent where removing an undeployed stack resulted in errors.
Corrected the title wording and some UI styling in the Authentication Logs and Activity Logs screens.
Resolved an issue with deploying of containers via Portainer running on Windows Server 2022, where an error regarding CAP_AUDIT_WRITE was occurring.
This is an STS (Short-Term Support) release. Read more in our .
Resolved CVE vulnerabilities for Windows images
Updated kubectl to resolve CVEs.
Resolved CVE vulnerabilities for docker binary
Resolved CVE vulnerabilities for protobuf
Resolved CVE vulnerabilities for crypto
Updated and Helm to resolve CVEs.
Updated Docker client library to resolve CVEs.
Resolved CVE vulnerabilities for stdlib
Resolved CVE-2024-29296 by creating uniform response time for login attempts.
Resolved a CVE regarding data encryption.
Updated Docker Compose to resolve CVEs.
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.
Resolved an issue that caused errors when users attempted to connect to their Docker environment via API using HTTPS
Provided info text in the UI to clearly explain environment variables stack.env file usage when deploying Docker stacks via Git vs. other methods.
Ensured confirmed support of vanilla Kubernetes 1.30 clusters.
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.
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.
Resolved an issue where pending actions to be run on environments would still be considered for deleted environments (although not actually run).
Resolved issue where containers that exited with code 0 were incorrectly marked as failed deployments
Introduced an additional option to automatically detect the authentication style for OAuth
Fixed the content type for responses from the API endpoint used for token generation
This is an STS (Short-Term Support) release. Read more in our .
Resolved an issue where Docker 25/26 API changes affected container-related pages and image size display
Resolved an issue where deploying GitOps edge stacks on a Kubernetes edge device resulted in error
Resolved an issue where the secret owner migration process could lead to a deadlock, preventing the HTTP(S) server from starting.
Fixed an issue where local stacks were being overwritten by orphaned stacks with the same name in the regular stack listing page
As you gear up for the transition to Portainer BE 2.20.0, our latest STS (Short-Term Support) installment, ensuring a smooth upgrade is key. We urge you to 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.
Read more in our .
Updated various packages to resolve CVEs.
Resolved an issue where deleting a Docker Swarm agent stack caused continuous error messages in logs
Resolved an issue where a Swarm stack failed to restart after being stopped when using private images.
Updated the version of the kubectl client in the kubectl shell console.
Fixed the stripping of labels from certain Kubernetes resources - Ingress, ConfigMap or Secret - when form-editing them.
Fixed an issue where namespaces 'set to system' from within Portainer weren't being detected as system.
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.
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.
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.
Fixed a 'this.formValues.Services is undefined' error that was shown when editing a pod created via manifest.
Resolved an issue where ConfigMaps and Secrets created via manifest were incorrectly shown with the 'External' badge.
Introduced a per-user option to enable five-minute data caching for non-edge Kubernetes environments - to improve performance.
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:'.
Introduced a setting to turn off the Stacks functionality within the Kubernetes side of Portainer.
Renamed the Kubernetes Advanced Deployment screen to be 'Create from Manifest'.
Corrected display of a very high 'CPU used' value in the Kubernetes Cluster details screen when micro-CPU units were being used.
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 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.
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.
Migrated the Kubernetes Application Details screen's YAML, Events and Containers sections plus any of the screen's remaining code from Angular to React.
Fixed an issue around the display of incorrect search results for Kubernetes applications that are exposed via an ingress.
Corrected the Kubernetes Volume Details screen to show the Shared Access Policy of the Volume rather than (erroneously) of the StorageClass.
Corrected the deploying of a Kubernetes Daemonset with shared storage so that RWX access is granted to the Persistent Volume Claim, as relevant.
Migrated the Kubernetes Cluster Setup screen from Angular to React and improved loading of its elements.
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.
Fixed a console error that could arise in the Kubernetes Add/Edit Application screen when updating resource sliders.
Corrected the labelling of the Stack field in the Kubernetes Advanced Deployment (now 'Create from Manifest') screen. Also clarified the labelling of Namespace and Name concepts.
Updated the Ingress list screen to indicate system resources correctly.
Fixed incorrect display of an error message when adding a Kubernetes secret under certain circumstances.
Made changes to allow stopping of a replicated Kubernetes application by scaling it to zero instances.
Migrated most of the components of the Kubernetes Create and Edit application screens from Angular to React.
Migrated the Kubernetes Add Namespace screen from Angular to React.
Ensured confirmed support of vanilla Kubernetes 1.29 clusters.
Added version path to in-app documentation links to support long-term support (LTS) vs. short-term support (STS) releases.
Resolved an issue with restoring from backup where portainer_data was stored on a network volume.
Resolved 'Unable to download backup' error that sometimes occurred when initiating database backup if portainer_data was sited on a network volume.
Resolved an issue with the upgrade and rollback process where the database was being backed up to a name that the rollback was not expecting.
Fixed a minor typo in the 'Back up Portainer' settings section.
Fixed an invalid commit link in the Stack details screen that could occur if the original copy/pasted Git URL of the stack was a GitHub repo URL with an extension of .git.
Introduced a UI fix to show a 'disabled input' cursor on hover of a toggle that's disabled for change (similar to existing disabled fill-ins, etc.).
Fixed a minor UI issue with the Environment -> Manage access screen enabling the 'Create access' button even though no changes had been made.
Enlarged a too-small font used in the Web editor's search/replace feature.
Improved Portainer navigation so all submenus now have their top-level option moved down to be the first option within their submenu and they always open to that. Implemented several other small menu improvements.
Improved the functionality around changing a linked environment's IP address so Portainer Server no longer needs restarting for the update to apply.
Introduced 'noindex' meta-tag to the Portainer login page to denote to search engines that the page should not be indexed and served in search results.
Improved styling and layout of headings and sub-headings throughout the user interface to improve legibility and hierarchy within pages.
Introduced success notification that was missing when adding a user to a team.
Improved styling of toggles throughout the user interface to make it clearer whether they are on or off, both when they are enabled for change or disabled for change.
Improved high contrast mode so that field borders, box selector text and expiry banners are easier to make out.
Improved high contrast mode to introduce a border around modals and tooltips so they are easier to distinguish from the rest of the screen.
Introduced support for input, copy and paste of extended Unicode characters in Docker container and Kubernetes kubectl shell consoles.
Corrected Swagger API documentation for the GET+POST /users/{id}/tokens endpoint so the example response describes the digest format correctly as a string, rather than (erroneously) as a list of integers.
Corrected Swagger API documentation which listed creation of custom template POST endpoints as /custom_templates/file (or repository or string), but should have listed them as /custom_templates/create/file (or repository or string).
Corrected API endpoint GET /webhooks documentation to describe filters parameter as a JSON string.
Resolved further Swagger API documentation problems including issues definition of GET /edge_stacks/{id}/logs/{endpoint_id}/file, GET /kubernetes/{id}/max_resource_limits and GET /kubernetes/{id}/namespaces/{namespace}/role_bindings.
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.
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)
Resolved an issue where polling and webhook methods failed to update the Stack
Resolved an issue where the Docker service page could not load correctly when the deployment was created using the GMSA credential spec parameter.
Introduced the ability for Helm chart repository searching and registry browsing to operate behind a forward proxy.
Improved security around non-admin user environment information access.
Resolved an issue where stacks that were initially deployed from a template could not be modified.
Resolved an issue where users couldn't define a proxy for the agent and edge agent when their network relied on a proxy for internet access.
Resolved an issue where pulling and redeploying Git stacks took longer than expected.
Resolved an issue where stacks triggered from webhooks were marked as inactive status, even though they were running as expected
Resolved an issue where users could interact with a console even after logging out from another tab in the browser
Resolved an issue where there was no warning for version mismatch between the server and edge agent, now UI clearly indicates matching server and edge agent versions are required for feature availability.
Improved security around non-admin users and their permissions.
Changes to API format and checking of some requests - See below for more details.
Fixed an issue where backup files were missing the Chisel private key. This could have disrupted communication between the Portainer server and agent after a restoration from backup.
Improved the upgrade process for the Portainer server, upgrade process now halts on database migration errors, preventing database version mismatches for a more stable environment.
Fixed an issue where toggles could be activated outside of their intended component area, potentially leading to inadvertent toggling.
Fixed API endpoints that were broken in the 2.19.0 release, ensuring that they retain their previous functionality.
Introduced new format around the change of a user's password via API.
Updated the checking around change of a user via API.
Select API endpoints are broken and will be restored in the next release:- see for specific details.
Updated the Docker Compose binary to v2.20.2, to resolve CVEs.
Updated the Helm binary to v3.12.2, to resolve CVEs.
Updated various packages to resolve CVEs.
Fixed an issue where deploying a large volume edge stack triggered a 'URI too large' error.
Introducing a new feature: , which simplify edge device configurations with GitOps. Effortlessly manage settings via version-controlled Git repositories for enhanced configuration control.
Improved logging for edge agent when polling fails. This enhancement provides more informative and detailed logs when polling encounters failures, aiding in quicker identification and resolution of issues.
Resolved an issue where users were able to create schedulers with an empty edge group, which is no longer allowed to ensure proper functionality and avoid potential errors
Resolved an issue where the edge agent default poll frequency selector was not lining up correctly
Resolved an issue where users were unable to create an edge group when there were no members present in that group. Edge groups can now be created without requiring initial members, offering greater flexibility in edge device and configuration management.
Introduce an enhancement to our snapshot creation process for edge devices which streamlines the snapshot creation experience, providing users with a more efficient and user-friendly way to capture snapshots on edge devices.
Fixed an issue where environment files were not functioning properly in Git deployments for edge stacks.
Introduced webhooks for edge stack, you can now set up webhooks for your edge stacks, enabling automated polling for GitOps updates.
Addressed an issue where the Docker client was not utilizing version negotiation.
Resolved an issue where the image name was displayed incorrectly when a user tried to duplicate or edit a container
Fixed an issue in the API where sending files to a Docker endpoint resulted in a panic.
Resolved an issue with Docker Proxy's performance, resulting in improved overall performance and responsiveness when using the Docker Proxy feature.
Resolved an issue in the Docker Container List where searching by published ports was no longer working.
Resolved an issue where '.' was not allowed in the image name (but should be) when building a Docker image via the UI.
Resolved some minor UI issues in Docker Services-related screens.
Fixed an issue in Docker Swarm version 24.0.0 where image tags were not being displayed.
Resolved an issue where clicking into the details page of a Swarm stack would redirect users to the service section instead of the top of the page
Adjusted Kubernetes Cluster setup screen's ingress settings to be clearer and to give info on ingress defaults.
Resolved an issue with Kubernetes ECR image pull where the secret token was not updating on manifest deployment.
Migrated the Kubernetes Add/Edit Application screen's Services section from Angular to React.
Reintroduced the ability to specify and use (via Add/Edit Application) ingress defaults (hostname and annotations).
Reintroduced the ability to publish via ingress from the Add/Edit Application screen.
Introduced correct redirecting of the user, following deployment of a Kubernetes manifest. Previously the user was always returned to the Applications List but will now arrive back at the screen from which they accessed the Advanced Deployment function.
Migrated the Kubernetes Application Details screen's Summary and Details sections from Angular to React.
Introduced a loading spinner to the Add/Edit ingress screen's ingress class dropdown, to indicate that available options are still being retrieved.
Resolved an issue that was occurring on the exposing of Portainer over a subpath, where Kubernetes Cluster Setup and other screens failed to load and reported an error.
Split the Kubernetes ConfigMaps & Secrets functionality in order to provide better performance and a clearer user experience. We now have separate tabs in the list screen and separate add/edit functions.
Resolved an issue with Kubernetes pages where a warning showed in the browser console ('findDOMNode is deprecated in StrictMode') when resource assignment was first toggled on for the namespace.
Updated Kubernetes ConfigMaps & Secrets terminology that was previously shown as Configurations, so as to align more clearly with Kubernetes.
In the Dashboard screen of Kubernetes environments, Ingresses and Services panels have now been introduced, providing a count of these resources and an easy means to click through and access their list screens.
Migrated Kubernetes Application console page from Angular to React.
Resolved a Node details issue where nodes showed incorrect role of 'Worker' due to deprecated 'node-role.kubernetes.io/master' K8s label (now 'control-plane'). Also where MicroK8s cluster nodes were incorrectly identified (though not due to labels).
Fixed an issue where a bad gateway response occurred when updating an environment with an empty URL.
Resolved an issue where users were unable to deploy a stack when utilising an image from a private GitLab registry.
To identify Portainer submenus more clearly, their sub-options are now indented.
Renamed "Automatic updates" in Git deployment section to "GitOps Updates" to clarify the feature at first glance for users. Please note this is a name change only and no functionality has been altered.
Resolved an issue with the App Templates screen, where a Kubernetes icon was incorrectly showing for Docker Swarm stacks. Also updated the Swagger API documentation to detail the existence of a 'Compose edge stack' App Template (numbered 4) type.
Resolved a minor UI issue where warning icons were smaller in size in multi-line warning messages.
Fixed an issue where standard users were unable to create Azure Container Instances (ACI) resources.
Fixed an issue where line break HTML tags were showing in some pop-up dialogs instead of actual line breaks.
Improved App Templates page with enhanced cursor icon and tile highlighting
Improved rolling back to CE from a CE to BE migration, by providing better logging and performing a check that the db file exists.
Fixed an issue where the primary environment remained permanently down after restoring from backup.
Introduced validation to prevent the use of invalid names when creating or editing Kubernetes or Docker Custom Templates.
Fixed an issue where the 'Skip TLS Verification' option was not functioning properly for custom templates.
Resolved a minor UI issue where multi-line text-tip and form-error icons were incorrectly vertically center-aligned rather than top-aligned.
Fixed an issue where the hover interaction for the environment tile on the homepage was missing
Fixed a security issue where usernames and passwords were displayed in responses.
Improved error logging in libhttp to provide more useful context.
Addressed an issue where TLS handshake error messages were being logged, which should only occur when using the DEBUG log level.
Resolved an issue where unnecessary snapshots were being loaded on the home page, leading to improved loading times and a smoother user experience
Resolved an issue where users were not being notified about the proper referencing of their uploaded .env files, requiring them to now utilize "stack.env" for appropriate referencing
Introduced a 'copy to clipboard' button to web editors within the Portainer UI.
Introduced the ability to manage time in seconds or milliseconds for container logs, expanding your time management options beyond seconds for more insightful troubleshooting.
Resolved a logging issue with database migrations, where, if an error occurred causing a rollback to the pre-upgrade version of the database, that error was no longer output to the console.
Resolved an issue that prevented users from stopping stacks with invalid project names during their upgrade from versions 2.6 or 2.7 to 2.13, 2.14, 2.15, 2.16, and subsequent versions.
Resolved an issue that prevented users from deleting stacks with invalid project names during their upgrade from versions 2.6 or 2.7 to 2.13, 2.14, 2.15, 2.16, and subsequent versions.
Resolved an issue where users were encountering difficulties when attempting to push images using a service principal account on Azure Registry.
Fixed an issue where delete confirmation modals were absent for edge stacks, Docker images, environment groups, and tags.
Fixed an issue where the creation of manifest file paths slice was incorrect.
Community contribution - The enhancement ensures that the response rewrite operation is properly wrapped with a valid status check, contributing to a more robust and reliable system behavior.
Fixed an issue where enabling GPU support on existing containers resulted in errors.
Addressed an issue where users were unable to update the TLS certificate for the Docker API environment.
Resolved an issue where incorrect AWS ECR icon was used when creating registry
Fixed a user interface issue where only up to 100 groups were being displayed.
Addressed an issue where using incorrect Azure registry credentials resulted in errors, even after updating with correct credentials, the issue persisted.
Resolved an issue where custom templates created from Git were not being pulled again at deploy time. This improvement has also been extended to Kubernetes custom templates.
Resolved an issue with new React version list screens where filter icons were not positioned next to the correct column heading but were abutting the next heading along.
Applied changes to the helper-reset-password utility to prevent it being accidentally used with the Docker Desktop Extension version of Portainer (where it could break access to the Portainer instance).
Replaced archived gorilla/securecookie library with just the function that we need extracted out.
Transitioned Edge stack environments table to React, delivering a more dynamic user experience with modernized interface, improved performance, and interactive management.
Documented 'excludeSnapshots' in Swagger API docs
Documented webhook types in Swagger API docs
Resolved a 2.0 validation error in our Swagger API documentation
We have updated the response for /endpoint to correctly reference 'EdgeCheckinInterval' in line with the accurate API Swagger documentation
Corrected missing type and 'file' to 'File' in Swagger API documentation for custom templates
Added descriptions to the Swagger API documentation for Kubernetes API endpoints that were previously missing from the docs.
Fixed an API issue where requests to create edge stacks with invalid deployment types were erroneously accepted
Addressed an issue in the 'edgeStackCreate' API where sending an incorrect request resulted in a 500 error response instead of the expected 400 error.
Fixed an issue in Swagger API documentation where 'endpointId' was incorrectly marked as optional. It is now correctly set as a required field
Corrected Swagger API documentation for starting or stopping stacks
Corrected 'ResourceId' and 'endpointId' as required instead of optional in Swagger API documentation for webhooks
Fixed the Swagger API documentation to require 'endpointId' when updating a stack
Corrected 'Endpoints' to be listed in alphabetical order in Swagger API docs
This release includes an experimental ChatGPT integration. Although it promises exciting possibilities, it's in the early stages of development. We recommend its use for testing and development, and urge caution in production environments. We greatly appreciate your feedback and understanding during this phase.
CVE-2023-28840
Upgraded Docker Compose version to v2.17.2 for Portainer Agent.
Resolve a problem building Portainer due to an issue with v1.53.0 of golangci-lint.
Resolved an issue where users were unable to migrate or duplicate their swarm stack.
Resolved an issue where the static IP addresses in a macvlan were unexpectedly changed.
Enhanced the user experience of the 'Skip TLS Verification' feature by adding a confirmation modal.
Resolved an issue where recreate containers fail when it has a shared and external volumes.
Resolved an issue where the response from the API was inconsistent when querying all endpoints and a specific endpoint.
Restored options and wording in the Kubernetes Advanced deployment screen's Automatic updates section, following regression from changes in 2.17. ()
Resolved issue preventing correct display of network details when containers are running on an unexpected Docker swarm node. ()
Fixed issue preventing LDAP server from creating a connection when using TLS 1.2. ()
Implemented minor UI changes to clarify existing experimental and beta features, ensuring accurate icon and wording display. ()
Corrected an issue causing the polling indicator to float incorrectly in UI when pulling Git repo list on the stack creation page. ()
Resolved syntax styling display issue in web editor. ()
Improved button color contrast in web editor. ()
Fixed visual hierarchy in web editor selection behavior. ()
Corrected 'team' to 'teams' in Swagger API docs. ()
Increased potential success rate of updating Portainer with larger databases by changing Kubernetes manifest and Helm chart for Portainer to have initialDelaySeconds of 45 (sec) and failureThreshold of 3.
Fixed issue where users were unable to pull the latest image from the image details page
Fixed issue where the option to skip TLS verification was missing when editing a stack created from git. Additionally, to adhere to security best practices, the option’s default value has been corrected to be set to off during migration
Fixed issue where TLS verification was being skipped when creating / editing stacks created from git in version 2.16.x
Resolved an issue with the updated web editor component, where it was not loading long YAML files correctly
For breaking changes in the API, please see the section.
Provide feature flag for FDO feature to be shown in UI
Fixed issue where live connect button is clickable for async environment when it shouldn't be
Removed "Add Edge devices" from Edge Compute and introduced to Environment wizard by renaming Edge Agent to Edge Agent Standard and introduced Edge Agent Async UI options
Fixed an issue where "copy token" button was missing from edge agent environment wizard
Fixed issue where live connect button is clickable for async environment when it shouldn't be
Improved performance of Kubernetes screens by adjusting rate limiting of Kubernetes go client.
Improved Kubernetes Applications page performance by introducing a namespace filter.
Improved Kubernetes Dashboard page performance.
Improved the load time of various Kubernetes pages by removing existing API calls that retrieve namespace resource quota information, where they are not needed.
Introduced a new Services screen in Kubernetes environments to improve the visibility of all services that may exist in a cluster, and enable removing where they've inadvertently been left behind after manual removal of applications/deployments.
Resolved an issue where default storage detection logic that runs on Kubernetes environment connection was incorrectly running on Docker environment connection, and was therefore causing an error to be output to the logs (but was otherwise benign).
Improved the existing UI around GPU support for Docker Standalone environments, introduced an overall toggle to turn this on or off and generally improved performance in Docker Containers and Stacks screens where GPU columns may show.
Fixed an issue where stack name validation was missing, causing deployments to fail
Resolved a minor UI issue with the Container details page's container health panel alignment and content label wrapping.
Fixed a typo in the placeholder text for the access control component's Authorized users dropdown where it said 'teams' but should have said 'users'.
Fixed issue where logs in JSON format displayed incorrectly in log viewer
Resolved an issue with slow performance of certain actions (such as bulk removing of unused container volumes or adding of Kubernetes ingresses) when a user has a long list of notifications (shown via the bell icon in the page header).
Resolved an issue that occurred when updating user preferences.
Introduced UI mechanism for automatic retrying of tunnel connection when it fails due to high latency
Added certificate support of AWS IAM Role Anywhere authentication for Agent and Edge Agent
Fixed issue where searching is not functional in associated edge environment when creating edge group
Fixed issue with Docker Swarm environment where containers count weren't displaying correctly in homepage.
Fixed issue where skipping https verification was default to true for Azure git deployment
Fixed issue where TLS Min Version was not fully enforced
Fixed a minor issue on restarting a container where the toaster pop-up message shown had an extraneous slash in front of the container name.
Fixed an issue while in dark mode, where, with any auto-filled text in fill-ins, the cursor completely disappeared until you started typing again.
Provide feature flag for FDO feature to be shown in UI
Fixed issue of missing requirement of TLS definition for endpoint creation and correct tagids parameter in swagger API
Improved Edge Agent Health status indicator and keep consistency with API response
Fixed issue where git deployment failed to edit or redeploy when compose path begin with slash
Fixed an issue in the restore from backup function, where a timeout error can occur and Portainer does not restart with the backup restored.
Improved the layering of the Portainer Dockerfile to ensure internal development-related aspects are excluded where possible.
Migrated git deployment page form Angular to React
Migrated code editor component from Angular to React
Introduced Tailwind prettier which will group utility classes project-wide and order them in a recommended way, making it easier to work with them.
Introduced replacement for bootbox with react components
Improved the feature flag architecture to make it easier to use.
Resolved incorrect usage of log.fatal to ensure the application exits only as necessary.
Fixed the API Swagger/OpenAPI documentation for some IDs that were defined as strings but should be integers.
Added to the API Swagger/OpenAPI documentation that you can upload a file to a Docker Standalone host when the host management feature is enabled.
Resolved the false positive report of Portainer binaries from VirusTotal.
Fixed issue with recreating containers in the Portainer UI if they have been originally created via the CLI.
Fixed an issue where upgrading to Business Edition leaves behind limited stack.
Fixed grammar of placeholder for region field in S3 backup configuration.
Fixed an issue where an error occurred for upgrading Portainer to 2.17.0 version when Docker engine version is 19.03.
For breaking changes in the API, please see the section
- Negroni
- golang.org/x/crypto/ssh in Go
- golang.org/x/crypto/ssh in Go
- net/http in Go
- Go
- javascript
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- kompose
- net/http in Go
Moved Edge Devices to the homepage view:
Introduced the ability to browse snapshots of async edge environments from homepage view:
Optimized performance for scaling large numbers of edge agents:
Introduced improved environment tile layout to address consistency when edge devices moved to homepage:
Fixed issue where edge stack incorrectly deployed to default namespace when there is a specified namespace defined in the manifest:
Fixed issue where select all checkbox is missing for edge stack and edge job tables:
Fixed issue with Edge device tags not showing on Create Edge Group screen:
Fixed issue where delete edge device does not remove it from the edge groups mapping:
The Kubernetes deployment option for docker-compose format manifests and the Kompose conversion tool that enabled this have now been removed due to long-standing Common Vulnerabilities and Exposures (CVEs) in Kompose:
Improved the explanatory tooltips and info text for Kube application automatic updates functionality:
Resolved an issue where Kubernetes secrets were no longer shown in an expand panel for each application listed in the Applications list screen:
Improved config setting defaults when connecting clusters: ingress controllers (with a class) are auto detected/set as allowed, metrics API features setting is on (if metrics server is deployed), and storage classes with the 'default' annotation are on:
Corrected the look of the fallback icon used for Helm charts that don't have their own icon:
Made a change to default the resource quota's resource assignment setting to off for new Kubernetes namespaces but always show the toggle (although it can be disabled for change if the cluster's (BE only) allow over-commit setting is off):
In the Kubernetes Add ingress screen, corrected the namespace selection dropdown to only show those that the user has access to:
Added a check in Kube Cluster setup and Namespace -> Manage access to see if Kube RBAC addon is enabled in the cluster, and if not, show a warning that Portainer RBAC functionality will be limited. Warning also gives info on enabling RBAC in the cluster:
Fixed an issue introduced in 2.16, where deploying of an ingress via the Portainer Add ingress form does not label the ingress object in the cluster with a Portainer 'internal' deployment label. Any deployment of ingress via Portainer should have this:
Fixed an issue introduced in 2.16, where, when attaching a ConfigMap to an application being deployed via the Portainer Add application form, the ConfigMap is wrongly included as a Secret in the manifest and the deployment could therefore fail:
Fixed an incorrect mention in the UI of a 'docker-compose file' which was showing when editing a Kube application deployed from git:
Fixed an issue preventing adding of a Helm repo that has a redirect:
Fixed an issue where the kubectl shell does not work when Istio Proxy is installed in the cluster:
Introduced support of relative paths for volumes when creating a Docker Standalone or Swarm stack that uses a git repository. Support in edge stacks is excluded at present:
Upgraded docker compose to v2.13.0:
Provided clarification and rewording in the UI around the 'Pull latest image' toggle in Stacks, Swarm Services and Service details update and Container recreate:
Updated embedded docker binaries in Portainer and agent from 20.10.13 to 20.10.18:
Fixed issue of not been able to associate stack created from other docker environments:
Fixed issue where content overlap edge of screen and left column becomes too narrow:
Fixed issue where default option for access control is not selected when editing public resource:
Fixed incorrect wording for private box selector under user access control:
Fixed issue where text input jumps to the end of the input box in repository form:
Fixed issue where scrollbar always visible in web editor form regardless contents of web editor:
Fixed issue where number of stopped container does not display in dashboard correctly:
Fixed an issue where deleting a network, config or secret did not show a confirmation warning modal:
Fixed an issue where a user cannot upload a stack file as a custom template:
Fixed an issue where the old-style UI was still being used in a Docker template-related page:
Fixed issue where new image notification only relies on checking first digest which is not always accurate:
Introduced support for S3 compatible hosts for backup and restore:
On the header context sensitive help icon, the red dot notification has been removed. This was put there to highlight the new feature in 2.16:
Upgraded version of golang.org/x/net from v0.0.0 to v0.1.0 for agent:
Upgraded jwt version to 4.4.2:
Improved Portainer tooltips to allow them to stay open long enough for clicking of links and selecting of text in them. Also left-justified them for better readability:
Resolved an issue related to revoking of user permissions:
Fixed issue where password could be leaked to the log files when errors occur:
Fixed issue when navigating to the login page log as a unique visitor in Matomo:
Fixed an svg attribute height error in the page (visible via the browser console):
Fixed typo where "occured" is used in error message instead of "occurred":
Fixed issue where long notification is pushed out of table making it hard to read:
Fixed incorrect link for other settings and agent setup:
Fixed issue where deleted environment does not clear in table and sidebar when deleting current selected environment:
Fixed issue where standard users were not able to change ownership to their own team:
Fixed issue where user encountered an error by deleting tags associated to deleted environments:
Fixed an issue where the 'hide for all users' button styling behaves differently in dark mode:
Fixed a minor issue where the pages and items per page elements in data table pagination controls did not quite vertically align with each other:
Fixed issue where team lead feature is unexpectedly enabled when external authentication is enabled with team sync:
Fixed issue where response from API when creating edge environments wasn't clearly specifying that URL is compulsory:
Fixed issue where internal authentication setting is not saved when switch from other authentication method without refreshing browser manually:
Fixed issue where user unable to remove group configuration with active directory authentication:
Replaced Feather svg icon set with Lucide, a Feather fork that is actively maintained and has a larger and improved range of icons:
Removed Font Awesome and all remaining references to it. All icons are now svg-based:
Redesigned Portainer database migration versioning to improve the robustness of the upgrade process:
Fixed issue where random number generator is not seeded causing predictable outputs:
Resolved issues building Portainer (caused by third-party deletion of the github.com/rkl-/digest package) by replacing the package with imported code. This provides HTTP Digest Authentication for Portainer's FIDO Device Onboard (FDO) protocol support:
Corrected a minor UI issue around a corrupted file-code.svg icon:
Removed the Go experimental module golang.org/x/exp, replacing the small amount of functionality that we use from it with direct code:
Deprecated the github.com/portainer/libhelm Helm wrapper and moved the code into CE, since EE can now share from CE. This is used by Portainer's Helm functionality:
Fixed issue where struct tag is malformed with incorrect blank space in template_file.go:
Fixed issue where the Git repository section is missing when creating an Edge Stack via the Git repository option.
Fixed issue where the effective viewer is not showing the correct user access role of environments they have access to.
Introduced the ability to auto-detect ingress classes in the environment.
Added an Ingress menu option in the sidebar that lists all Ingresses in the cluster.
Introduced the ability to set the type of a Kubernetes secret (e.g. TLS or a user-defined/custom type). Existing secrets were previously always of type Opaque (which remains the default).
Improved ingress options on the cluster setup page, allowing admins to define ingresses without assigning them to a namespace.
Introduce TLS and HTTPS support for ingresses.
Moved the Ingress management from the Application details page to a new Ingress section.
Resolved an issue when OAuth is in use and Kubernetes updates are deployed via manifest from git. The user email address used in labels/annotations for Kube objects now has disallowed characters (such as the at symbol) replaced with a dot (period symbol).
Resolved an issue where Node stats would not work for Google Kubernetes Engine (GKE) clusters.
Fixed the issue of missing Kubernetes definition for Kubernetes application deployment in the swagger API documentation.
Updated the Compose version to 2.10.2.
Added support for shared memory when creating or editing a container by allowing to set --shm-size from portainer.
Introduced support for uploading of local files to be included in a Docker image when using Portainer to build an image.
Introduced a setting to turn on/off per host showing of out-of-date image indicators.
Added information for rebuilding images from stacks on docker standalone environments.
Added information to the build image from the URL page, including a link to additional documentation.
Fixed an issue where environment variables for stacks could not be set to empty.
Fixed an issue where assigning user access to a stack, showed users that don't have access to the Environment.
Fixed the issue of missing agent deployment script for the docker standalone environment.
Fixed the issue of the misconfigured stack being saved and subsequently can not be deleted.
Fixed an issue where the Swarm secret values incorrectly were being trimmed.
Fixed an issue where the Docker API section in the add environment wizard incorrectly was showing the docker.sock code block.
Fixed an issue where renaming a deployed container resulted in an error.
Fixed error message when adding new docker environments with invalid CA certs for TLS.
Adjusted the "remove" buttons as per the UI guidelines that were introduced in the 2.15 release.
Introduced a new section that shows past toaster notifications, which are stored in the browser's local storage.
Introduced a context sensitive help button that links to the relevant documentation based on the current page.
Updated dependencies of PCIDB/GHW for the portainer agent.
Updated version of chart.js to 2.9.4 and moment to 2.29.4.
Updated binary version for docker-compose and helm (to v3.9.3).
Updated the agent library dependencies.
Fixed an issue where the browser tab title did not update with the actually selected environment.
Fixed issue where the dropdown menu has incorrect background color in dark mode.
Fixed styling issues in the Runtime & Resources tab.
Fixed an issue where the new styling wasn't being applied to links.
Adjusted the warning text color as per the UI guidelines that were introduced in the 2.15 release.
Removed extension validation from compose path field.
Fixed an issue where the Group and Tag could not be set for Nomad environments when adding it via the wizard.
Fixed an issue where Nomad system jobs would prevent other jobs from being shown.
Improved unit tests by using T.TempDir to create a temporary test directory.
Replaced the logrus logging framework with Zerolog.
Fixed an issue where new installations that use the develop branch didn't apply the analytics setting correctly.
Fixed an issue with connecting to the local Docker environment when using Windows Container Services.
Fixed an issue where the build image button would stay inactive when using a tar file.
Fixed an issue where some colors in dark mode appeared too brown.
Fixed an issue when using leading or trailing spaces in a password would break the login process.
Proposing to deprecate Kompose and remove the functionality to deploy compose yaml on Kubernetes.
Improved caching to prepare a resolution for an issue where certain browsers need a manual browser refresh for new version assets to load. The change only takes effect for upgrades subsequent to migration to 2.15.
Introduced an option to forcibly remove a Kubernetes namespace that's in a 'Terminating' state.
Improved the kubeconfig download dialog by providing pagination (including choosing of the number of items per page), an option to 'select all in page' and selection across multiple pages.
Resolved an issue where the link shown for an application that is exposed via an ingress was including an incorrect port (the servicePort).
Added GPU support to Docker containers.
Added support to read value from .env in subfolder for git deployment in Docker Standalone Environment.
Added message explaining that changed env values only take effect after redeployment or auto update via webhook.
Provided prune option for stack deployment from Git.
Removed "Show Container Template" toggle on App templates page and introduced filter and sort by dropdown options.
Fixed recreate of container so it pulls the image using the SHA256 hash if its tag no longer exists, and if the image is still inaccessible (as it no longer exists or the tag or name is now incorrect) warn the user and disable 'Pull latest image' option.
Introduced improved validation to the Docker build image function, to prevent invalid image names.
Fixed host info being sent when host management feature is turned off.
Following the introduction of v2 Docker Compose, changed any front-end wording that mentions 'docker-compose' to say 'docker compose', to clarify and bring in line with official documentation.
Introduced new styling for Portainer.
Introduced Portainer UI redesign with changes for common configuration pages.
Included build information in Portainer for easier debug.
Introduced the ability to show/hide the password you are entering on login.
Introduced CTRL+F (or CMD+F on MacOS) to search in web editors.
Introduced the ability to filter connection type and agent version on the home page.
Improved environment address entry to handle http:// or https:// prefixes when adding an environment via Docker or Kubernetes (agent) options.
Introduced a change to the Homepage's multi-select filters to keep the dropdown open after a single selection until the user closes it themselves, or the last remaining option is selected.
Updated the agent library dependencies
Fixed issue of authentication logs not working behind reverse proxy.
Fixed a few typos in various locations.
Fixed issue with environment page table losing selection on table refresh.
Fixed missing BE feature indicators.
Fixed issue where certificate uploading is not functional for StartTLS/TLS in LDAP configuration.
Updated UI of Add devices page to match the Add environment page.
Fixed issue where editing edge jobs changed the configured cron expression.
Removed Beta label on Edge Jobs.
Improved Registry details screen with better prompting for relevant fields.
Resolved an issue around not being able to add multiple Quay registries.
Improved the Registry details screen to show the registry provider and made the Add registry screen default to Docker Hub as the provider.
Fixed an issue where the kubeconfig downloadable from Portainer always had port 9443 in its URLs, even though the actual Portainer instance was being accessed via another port.
Fixed certificate file validation for .pem files
Fixed an issue where the original admin user was unable to change their password when external authentication is enabled.
Fixed toggle state reset issue for custom logo and anonymous statistics.
Fixed issue with not being able to add users to teams while LDAP authentication is enabled without auto teams population.
Fixed pagination issue on Add edge jobs page for listed environments.
Resolved an issue where users running Portainer with non-root access were receiving a 'Permission denied on docker-compose' error since the recent update to Docker Compose V2.
Resolved an issue where users upgrading a Portainer install, where the portainer_data volume is stored on a network volume, receive a 'Permission denied' error when the upgrade attempts a backup of the database.
Fixed "Create user" button in disabled stage when external Auth enabled.
Fixed issue where the edge agent could not connect when running Portainer behind a reverse proxy only supporting TLS v1.2.
Fixed issue around Git clone working with Main (in addition to existing Master) branch type.
Updated packaged components to recent stable release versions: Docker 20.10.9, Docker Compose plugin 2.5.1, kubectl 1.24.1, Helm 3.9.0.
Fixed a typo in the Kubernetes -> Namespaces -> Create from manifest (advanced deployment) page.
Introduced a visual indication of stacks, services and containers that are running with an out-of-date image.
Fixed issue around Git clone working with Main (in addition to existing Master) branch type.
Updated packaged components to recent stable release versions: Docker 20.10.9, Docker Compose plugin 2.5.1, kubectl 1.24.1, Helm 3.9.0.
Fixed issue for standard user having an empty network as default when creating containers on Windows environments
Provide a stack template for dokku deployment within portainer.
Resolved an issue when updating an application and changing its service from replicated to global, where an error occurs and the deployed application is deleted.
Fixed an issue where, when calling Swarm update API through Portainer, incorrect overriding of the registry authentication header occurred, preventing pull of an image.
Redesigned team leader feature.
Fixed an issue where the delete environment confirmation dialog was positioned too low on-screen.
Fixed an issue where agent and edge agent install command instructions do not list the agent_secret option.
Fixed an issue where the home (environments) page no longer showed the words 'No tags' for environments without tags.
The Add environment page and Environment wizard are now consolidated into a single consistent, improved wizard-style experience.
Fixed Go panic state for the environments list handler
Introduced ability for admin to set required password length.
Increased the click/touch area in expandable panels so it's easier to open/close them.
Fixed issue with status indicator on Edge Stacks not updating when removing tags from edge environments/groups
For edge agents, the URL shown in the Environment summary page (access from the Home page) has now been removed, as it caused confusion since it simply showed the Portainer Server URL.
Fixed Data race in the operations of the edge key in the Edge Agent
Added "goto page" to the Edge devices page view
Added the ability to add edge agents in the environment wizard
Added display of BE feature highlights in CE for new Nomad, KaaS provisioning and kubeconfig import functionality.
Changed the minimum TLS version of Portainer from 1.3 to 1.2 to avoid issues with nginx reverse proxies:
Fixed issue with the Portainer authentication settings page not being able to save:
Changed the password policy to require 12 characters for all Portainer internal users:
Improve how Portainer helps you set up ingresses (especially Nginx ones), including support of regular expressions in paths - by assisting with required annotations and correcting a rewrite issue:
Fixed an issue where, on setting up (on a namespace) an ingress controller for a k8s cluster and I create an app with two ingress routes on the controller, app details show only the second of the paths:
Fixed an issue where Portainer's validation of a K8s namespace's hostnames was disallowing wildcards (e.g. *abc.com):
Fixed issue with default helm repo not populating in settings page:
Created documentation around using GKE ingress with Portainer:
Added input validation for kubernetes workload names:
Fixed issue where Helm Charts could not be deployed when using SSL certs with Portainer:
Fixed issue of not being able to use a name previously used for kubernetes resources:
Fixed issue where the Kube cluster resource stats had a rounding issue:
Fixed an issue when deploying Portainer client with AGENT_SECRET without configuring Kubernetes agent with AGENT_SECRET where an "Failure unknown" error shows rather than "agent already paired" :
Fixed issue where the Disable bind mounts for non-administrators setting would prevent existing volumes from being used:
Fixed issue with creating a CIFS volume that uses a hostname:
Fixed issue where webhooks for services were accepting invalid tags:
Fixed issue with libcompose logging where error output is attempted to be included when an error did not occur:
Fixed an issue where 'Pull and Redeploy' and 'Force redeploy' don't work on ARM:
Documented deviation from the Docker standard when using the /docker/images/create API endpoint in conjunction with a private registry:
Fixed issue where credentials from different registries were being used:
Fixed issue where stack name was stated inaccurately in the message which informs users that a container/service inherited its access control settings from a specific stack:
Fixed issue with displaying container template when connected to docker swarm in the app templates page view:
Fixed text color on modal when updating a service:
Fixed issue where Watchtower did not work for standalone stacks on Arm64:
Enforced strong password policy for all Portainer Users:
Improved the database migration to become more resilient:
Introduced the ability to filter and sort environments on the Home page:
When changing the user password the user gets redirected to the login page:
Improved security for custom templates when using Git repos that contain symlinks:
Improved how the installation page times out:
Fixed bug relating to environment status in home page:
Improved concurrency in agent code to prevent race conditions:
Improved concurrency in backend code to prevent race conditions:
Fixed duplicate naming issue for registries:
Fixed issue around user accessing agent environment after changing an invalid environment url to a valid one:
Fixed issue with the menu when connecting to another environment fails:
Updated registry form wording from Password to "Dockerhub access token" :
Fixed an issue where the hover-over tooltip for nav menu items always just showed 'Settings' rather than the menu item text:
Fixed issue where the green success notification was not showing up after deleting a custom app template:
Improved UX for setting themes by removing save button:
Resolved data race on stack deploy for edge agents:
Added environment variable to the agent to adjust the probe timeout and interval:
Introduce the ability to pass env variables from a local system on edge devices to the edge stack:
Fixed issue with edge environments having faulty heartbeat on Edge Devices page:
Improved concurrency in edge code to prevent race conditions:
Fixed data race in poll service on Edge Agent:
Resolved some race conditions with the edge agent:
Resolved data race on tunnels for edge agents:
Resolved data race with activity timer for edge agents:
Fixed issue with displaying AMT device table for non-activated devices:
Fixed minor UI issues in Edge devices page view around Action buttons:
Fixed issue when creating edge job from file returning 404:
Updated the Go library dependencies:
Migrated AngularJS components to ReactJS:
Reorganized the file structure of the agent installation yaml files:
Removed the integration with Storidge clusters:
Improved concurrency in edge code to prevent race conditions:
When OAuth is enabled, Portainer users can no longer use their Portainer internal password:
Added input validation for kubernetes workload names:
Fixed issue where the Kube cluster resource stats had a rounding issue:
Migrated to use the networking.k8s.io/v1 ingress API, available from Kubernetes v1.19:
Allow Services to be managed for Kubernetes applications, which can be deployed within Portainer or outside of it:
Restarting Portainer will no longer result in invalid kubeconfig credentials, which would have required the user to download a new kubeconfig file again:
Provides a single process so that users can gain access to all their environments contexts from within the Portainer UI:
Improved how a namespace gets selected when using Advanced deployment:
Added warning that a secret will be created when adding registry access to a namespace:
Fixed issue where selecting a Helm chart did not scroll to the top:
Fixed issue when clearing Helm repo in global settings and added text notification in Helm charts page:
Fixed issue where Helm charts fail to load in ARM cloud environments:
Fixed issue where the kubectl shell wasn't working when Portainer runs on ARM64:
Fixed bug so that Kubernetes terminology is used when deploying through Kubernetes:
Fixed issue where error notice was coming up when deleting an application through kubeshell:
Fixed issue where Portainer stacks were not being removed when removing a namespace:
Fixed issue where standard users were unable to access the pod and node stats view:
Fixed issue where the namespace details page showed an object object error:
Fixed issue when selecting Cluster Setup in the menu:
Fixed order of registries to be alphabetical in the select registry dropdown in namespaces:
Fixed issue with publishing method defaulting to Ingress when changing to Cluster IP:
Introduced the ability to pull latest images when redeploying:
Fixed issue where webhooks for services were accepting invalid tags:
When updating a Swarm service and enabling Pull latest image, it would change the tag to latest:
Fixed issue where updating the Stack always recreated the containers:
Added the ability to filter the Swarm services published ports column:
Added a warning when the same Swarm secret is assigned multiple times to a service:
Added the option to detach Stacks deployed from Git to make them editable:
Removed the ability to edit the Portainer container:
Fixed issue where an error message would not be shown when failing to pull an image:
Fixed issue where the default user for the container console was incorrectly auto filled:
Fixed issue where uploading large files to a volume would fail:
Fixed issue where stacks deployed from App Templates behaved as if they were deployed from Git:
Fixed issue where stacks with environment variables in the networks section could not be removed:
Allow the resource settings of a container to be updated without redeploying the container:
Added support for .bz2 and .xz compression formats when importing Docker images:
Enhancement of the Docker image import feature to support manually adding tags to the imported image:
Improved how to change the image when editing a Service by pre-populating the fields in the UI:
Fixed issue where automatic updates of stacks fail after restarting Portainer:
Fixed issue where pull and redeploy button was not functioning as expected:
Fixed UI issue when using a personal access token to deploy from Git:
Fixed issue where certain docker events showed as Unsupported:
Fixed issue with stack names when migrating from Swarm to docker standalone:
Fixed issue where migrating a stack shows up twice:
Fixed issue where using a webhook with an image registry running on a custom port did not work:
Fixed issue where downloading container log files added extra carriage returns:
Fixed issue where copying container log files added trailing commas:
Fixed issue where the scale labels of the stats graph was showing multiple times:
Fixed issue where stats were not working on windows containers:
Fixed UI issue with empty stack dropdown when deploying an application via the form:
Fixed issue with Custom Template on Docker being created when the file does not exist on a git repo:
Fixed trivy Helm and Portainer vulnerabilities relating to direct dependencies.
When changing the user password the user gets redirected to the login page:
Fixed ability for a Standard User to start/stop stacks
Removed the integration with Storidge clusters:
Changed the default Microsoft OAuth logout URL:
Portainer users can no longer use their Portainer internal password when OAuth is enabled:
Option to encrypt values in Portainer database:
Added the ability to override the "Force HTTPS only" option:
Supporting the ability for Portainer to run inside a subpath:
Updated the defaults for the Git authentication toggles:
Fixed display issue for environment tags in the Home page view
Fixed issue where scrollbars would show in confirmation dialogs:
Fixed issue where the --sslcert flag was being ignored:
The ability for users to easily interact with the Portainer API through the use of Personal Access Tokens:
Automatically sync Portainer dark/light theme with the browser dark/light theme settings:
Fixed issue where the CPU and memory were not shown on the Home screen:
Added confirmation modal when deleting an Environment:
Fixed issue where removing an environment did not update the tree:
Fixed issue where the DockerHub anonymous registry was being used instead of one with an account:
Fixed issue where environment displayed as offline after starting Portainer:
Fixed issue where the custom logo settings showed incorrectly in the UI:
Fixed issue where uploading a backup file could not select a file on Mac:
Fixed issue where apple touch Portainer icon had non standard image dimensions
Fixed issue with widget header not displaying correctly for application settings:
Introduced the ability to control and interact with OpenAMT: devices
Introduce the ability to add edge devices through FDO:
Added behavior for Edge agents to reject connections if not connected to within 72hrs:
Optimize disk performance for Edge Agent
Fixed issues with the Edge Agent reverse tunnel timing out:
Fixed issue where the URL of an Environment would change to localhost:
Fixed issue with duplicating registries during upgrade process.
Bring users the ability to use Amazon Elastic Container Registry:
Fixed issue where ACI stopped working when the number of exposed ports and container ports were different:
Upgraded golang version to 1.17
Updated the Swagger documentation:
Deprecated EndpointProvider in the code and moving away from its use:
Introduced ReactJS support in the frontend:
Updated docker and kubernetes library dependencies:
Updated the Swagger documentation:
Added logging to migrations:
Both Portainer and the Agent need to be upgraded at the same time:
Restarting Portainer will invalidate all downloaded Kubeconfig files:
Default HTTPS support has been added:
The /stacks API has renamed from ComposeFilePathInRepository to ComposeFile, and the non-mandatory fields AdditionalFiles and AutoUpdate were added:
It is advisable to upgrade to this version, since some security improvements have been made with regards to embedding images:
Introduced the ability to open a shell in Portainer to use kubectl:
Introduced the ability to download a kubeconfig file and use Portainer as a proxy:
Introduced the ability to install Helm charts:
Introduced the ability to use any public Helm repository:
Introduced the ability to automatically sync a manifest from a git repository:
Introduced a visual indicator for applications to see if they're fully replicated:
Introduced the ability to filter Kubernetes applications by type:
Introduced the ability to remove all workloads of a manifest based deployment:
Added the ability to display Helm chart deployments in the applications list:
Added the ability to update and redeploy an application created from a git repository:
Added support for deploying images stored on private registries for Docker and Kubernetes:
Introduced the ability to mark and unmark namespaces as system:
Added functionality to define a manifest as custom template:
Added the ability to deploy a manifest from a URL:
Added memory and CPU usage indicators to the namespace and cluster details:
Added status information to list of namespaces:
Added Pod IP address information to the application details:
Added input validation when adding an ingress:
Improved the validation of resource allocation available on any of the nodes when adding an application:
Improved UI so that accessing the advanced deployment functionality is similar to accessing the form:
Renamed configuration and the networking area in the UI:
Improved UI for the metrics API toggle in the cluster setup:
Removed validation of any ingresses that are already in use in other namespaces:
Introduced the ability to use Edge Stacks on Kubernetes via edge agents:
Added warning that a secret will be created when adding registry access to a namespace:
Fixed issue where the metrics server API was being queried when disabled:
Fixed issue where the node events would not be showing:
Fixed issue where applications deployed via Helm in Portainer were marked as external:
Fixed issue where the kubectl shell would close when performing other actions:
Fixed issue where the kubectl shell wasn't working when Portainer runs on ARM64:
Fixed issue where the cluster status was incorrectly shown:
Fixed issue where the application details incorrectly showed how it was deployed :
Fixed issue where standard users were unable to access the pod and node stats view:
Fixed issue where editing an application could not expose it via Ingress:
Fixed issue when clearing Helm repo in global settings and added text notification in Helm charts page:
Fixed issue where Helm charts fail to load in ARM cloud environments:
Fixed issue where the namespace details page showed an object object error:
Introduced the ability to automatically sync a stack from a git repository:
Introduced the ability to use stacks on docker standalone on ARM64:
Introduced the ability to use Edge Stacks on ARM64:
Added support for deploying images stored on private registries for Docker and Kubernetes:
Added the ability to edit a stopped stack:
Added the ability to edit environment variables for stacks on docker standalone:
Docker container stats graphs now support cgroups v2:
Improved how to change the image when editing a Service by pre-populating the fields in the UI:
Fixed issue where all images regardless of their tag would be pulled:
Fixed issue where volumes would lose their access control settings:
Fixed issue where standard users were unable to browse volumes created by stacks:
Fixed issue where ports would show for IPv4 as well as IPv6:
Fixed issue where container_name validation would not take stopped containers into account:
Fixed issue where editing a stack would warn about the container name being in use:
Fixed issue where navigating away incorrectly showed a changes not saved popup:
Fixed issue where the stack name would contain spaces or upper case characters:
Fixed issue where the UI would incorrectly report that an image was successfully pulled:
Fixed issue where the Stack editor would not always load its content:
Fixed issue where environment variables were incorrectly showing when the value contained an equals sign:
Fixed issue where the browser console would show errors in the container and image details view:
Fixed issue where dashes and underscores in stack names were being removed:
Fixed UI issue where adding a Service with a mix of TCP and UDP was being prevented:
Fixed issue where images could be used in custom templates notes:
Fixed issue where automatic updates would keep polling when the user that created the stack is removed:
Fixed issue where automatic updates of stacks fail after restarting Portainer:
Fixed issue where stack names were not being validated when using custom templates:
Fixed issue where stats were not working on windows containers:
Fixed issue where the scale labels of the stats graph was showing multiple times:
Fixed UI issue when using a personal access token to deploy from Git:
Fixed UI issue with empty stack dropdown when deploying an application via the form:
Fixed issue where migrating a stack shows up twice:
Introduced dark theme and high contrast mode:
Introduced the ability to access Portainer via HTTPS:
Renamed Endpoints to Environments in the UI:
Improved the menu UI to indicate the existence of sub items:
Improved UI how to add environments to Portainer when doing a new installation:
Added functionality to copy error messages from toast notifications:
Improved how a Portainer upgrade can be rolled back:
Improved UI where the table background wasn't working very well in dark mode:
Fixed issue where Git content could not be cloned when Portainer is behind a proxy:
Fixed issue where the SSL certificates were not included in the Portainer backup:
Fixed issue where editing an endpoint results in errors:
Fixed upgrade issue where disconnected endpoints caused the upgrade to fail:
Fixed issue with the layout of the add Environment Wizard:
Fixed issue where the custom logo was not used in all places:
Fixed issue where the DockerHub anonymous registry was being used instead of one with an account:
Fixed issue where upgrade fails:
Fixed issue where the Quick Setup wizard wasn't showing correctly when using the dark theme:
Fixed issue where uploading a backup file could not select a file on Mac:
Fixed issue where the URL of an Environment would change to localhost:
Added a build for Windows Server 20H2:
Added a build for Windows Server 21H2:
Improved UI to provide information for correctly using a ProGet registry:
Fixed UI issue where the registry list incorrectly showed that there's no registry available:
Fixed issue where ACI stopped working when the number of exposed ports and container ports were different:
Fixed issue where ACI would show errors when a resource group had multiple containers:
Introduced the ability to use Edge Stacks on Kubernetes via Edge Agents:
Introduced the ability to re-associate an edge endpoint to a new Edge Agent:
Improved the REST API access of the Edge Agent in Docker standalone:
Fixed issue where the heartbeat indicator was not reliable:
Fixed issues with the Edge Agent reverse tunnel timing out:
Added the ability to query the endpoints by type through the Portainer API:
Integrated with Logrus for the internal logging mechanism:
Updated the Golang version to 1.16:
Improved the Portainer API documentation for adding users:
Fixed inconsistencies in the Portainer API documentation:
Updated the Swagger documentation:
Host Management features do not work on Windows Hosts