Update docker.io/portainer/portainer-ce Docker tag to v2.39.1

Update docker.io/portainer/portainer-ce Docker tag to v2.39.1
Photo by Dominik Lückmann / Unsplash

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 (source) patch 2.39.02.39.1

Release Notes

portainer/portainer (docker.io/portainer/portainer-ce)

v2.39.1: LTS

Compare Source

Known issues

  • On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot
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

Changes

  • Fixed an issue where a Git-based Docker stack from GitLab failed validation for non-admin users
  • Re-enabled image registries for FIPS
  • Fixed an issue where groups were missing after an upgrade
  • Fixed an issue where not all containers for a service were shown in v2.39.0 Alpine
  • Fixed an issue where users could not add new environments to an existing group when the group already contained a large number of environments
  • Fixed an issue where the Edit this application button was disabled for non-admin users
  • Fixed an issue where custom template file content was accessible to unauthorized users
  • Fixed an issue where users could not view their containers
  • Fixed an issue where users saw a blank dashboard
  • Updated the kubectl shell image to version 1.35.2
  • Updated Kubernetes to version 1.35
  • Updated Go to version 1.25.8 to mitigate the following CVEs:
    • CVE-2026-25679
    • CVE-2026-27142
    • CVE-2026-27139
  • Resolved the following CVEs:
    • GO-2026-4550
    • GO-2026-4473
    • GO-2026-4394
    • CVE-2026-24051
    • CVE-2025-68121
    • CVE-2026-33186

Deprecated and removed features

Deprecated features

  • None

Removed features

  • None

Read more

Me on Mastodon - This link is here for verification purposes.