Update docker.io/portainer/portainer-ce Docker tag to v2.39.0
No problems deploying to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach with dependency update facilitated by Mend's Renovate Bot.
Also the corresponding agents were automatically rolled out via Watchtower infrastructure on the Docker-only nodes including arm node with dependency update facilitated by Mend's Renovate Bot.
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| docker.io/portainer/portainer-ce | minor | 2.38.1 → 2.39.0 |
Release Notes
portainer/portainer (docker.io/portainer/portainer-ce)
v2.39.0: LTS
Known issues
- On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
Known issues with Podman support
- Auto onboarding a Podman environment defaults to "Standard" and not "Podman"
- 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
Changes
- Fixed an issue preventing environment group changes for Kubernetes standard agents from the environment details view
- Addressed security vulnerability disclosure
- Updated form behavior to only show errors after the input has been touched/visited or submitted
- Improved HTTP response code handling via the Portainer API
- Added default alphabetical sorting to the namespace dropdown list
- Fixed a UI issue where the dropdown form elements were overlapping with the footer
- Updated styling of shared tabs used throughout Portainer
- Improved TLS initialization for custom registries
- Fixed a memory leak in kubectl delete
- Fixed an issue where a ""Release: not found" error was presented when installing a Traefik ingress
- Fixed an issue when editing an environment that could inadvertently remove unix:// from URLs
- Reordered the agent options in the "Add Environment" interface
- Fixed an issue where Portainer was unable to pull from a private registry with a port in the URL
- Fixed an issue where a webhook was missing during the initial deployment
- Fixed an issue where the API response code from /docker/containers/create was returning 200 instead of 201
- Improved visibility of the "New version available" alert in light mode
- Upgraded package versions to mitigate potential frontend vulnerabilities
- Associated environments in a group will now only be saved when submitting the form
- Updated the documentation link supplied in the Portainer logs when a user tries to start Portainer BE with a CE database
- Fixed a 500 issue when loading Docker in the dashboard
- Fixed a problem with GitOps removing containers when image pull fails
- Fixed incorrect transaction usage around webhooks
- Fixed incorrect transaction usage when deleting endpoints
- Resolved the following CVEs:
- CVE-2025-61726
- CVE-2025-68121
- GO-2026-4337
- CVE-2025-15467
Deprecated and removed features
Deprecated features
- None
Removed features
- None
