Portainer's Community Edition stops at 2.45 LTS

Cresswell's 11 September post on the Portainer blog argues from maintenance cost ^[1]. Policy management, the operations API and the internal auth model each had to be built three times, once per substrate ^[10]. Three subsystems on three substrates is nine implementations to keep in step, and three copies of an auth model is three places for one bug to live ^[1]. A dev.to writer who runs Portainer for half their Docker clients summarised the post. By that account, Cresswell's view is that a single fully featured codebase across Docker/Podman, Swarm and Kubernetes stopped being realistic ^[10][22].

The second argument is about AI agents. Portainer says Docker and Swarm have no equivalent of Kubernetes network policies, pod security standards or admission controllers, which are the primitives it wants for sandboxing autonomous agents ^[11]. I find the build-cost argument the stronger of the two, because it concerns code Portainer already ships. The agent argument explains why the surviving substrate is Kubernetes ^[11].

The free option now works differently. According to the dev.to writer, free use from 3.0 on is a Portainer Business licence tied to an account, not a community-maintained build ^[15]. Community Edition stays on 2.x and does not get 3.x features ^[4]. Cresswell's clarification covers what is already installed: "nothing that works today gets ripped out of 2.x or the Docker environments in 3.x," he said ^[13]. He also said that if Docker support ever reaches end of life, users will hear about it well in advance and get a migration path ^[14].

Staying on 2.x leaves one date open. The dev.to account does not give an end-of-support date for 2.45 LTS. It points to Portainer's lifecycle docs for the support timeline ^[20].

Leaving means picking a Docker-first tool. On single boxes the writer runs Dockge, an MIT-licensed Compose stack manager from the Uptime Kuma author that edits compose files directly ^[16]. For several client hosts that need GitOps, the writer uses Komodo, which is GPL-3.0 and handles multi-server Docker deployments ^[17]. Dockge compose files port to Komodo unchanged, according to the writer. A client who starts on one box does not have to be rebuilt when they add hosts ^[17]. Arcane offers a Go-based UI, and Coolify and Dokploy cover git-push deploys with automatic SSL ^[18].

On timing, the writer wrote: "None of this is urgent: if your homelab runs Portainer 2.45 CE today, nothing breaks tomorrow." ^[21]