portainer

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

Michi Kofler-Häusler

25 Oct 2025 — 1 min read

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.34.0` -> `2.35.0`

Release Notes

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

`v2.35.0`: STS

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

New in this release

Fixed a bug where the Edit Ingress page wasn't displaying updated information immediately after making an update
Fixed an issue where GitOps webhook URLs could be reused
Fixed a data race issue caused by the Kubernetes client
Fixed an issue that caused a memory leak when redeploying a Kubernetes stack
Fixed an issue where the environment status filter did not properly handle the "Failed" state when used with Edge Stacks
Added support for IPV6 network configuration for IPvlan Docker networks
Added a new command flag --compact-db to allow database compaction on startup
Fixed typos in Content-Security-Policy
Added support for Helm GitOps allowing automatic upgrades based on changes to a Helm chart and/or Helm override files in a Git repository
Fixed an issue with access control when users attempted to view resources in namespaces they don't have access to
Fixed an issue where WebSocket connections were not forwarded correctly to the Kubernetes API
Fixed missing dependency versions in popup
Resolved the following CVEs:
- CVE-2025-7783
- CVE-2022-37601

Deprecated and removed features

Deprecated features

None

Removed features

None

Update docker.io/b4bz/homer Docker tag to v25.10.1

No problems automatically updating the Docker image and run the container by Watchtower for website Bierochs with dependency update facilitated by Mend's Renovate Bot. v25.10.1

Update docker.io/hashicorp/vault Docker tag to v1.21.0

No problems upgrading the Hashicorp Vault Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change docker.io/hashicorp/vault minor 1.20.

Update docker.io/ghost Docker tag to v6.5.1

On both domains I upgraded Ghost successfully by means of Watchtower Docker container update with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change docker.io/ghost minor 6.4.0 -> 6.5.1 Release Notes TryGhost/Ghost (docker.

Update ghcr.io/home-assistant/home-assistant Docker tag to v2025.10.3

No problems deploying Home Assistant patch version 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. This MR contains the following updates: Package Update Change ghcr.io/home-assistant/home-assistant (source) minor 2025.