Three clients messaged me this week asking some version of "did Portainer just
kill Community Edition?" Not exactly, but if you run Portainer CE on a homelab
box or a client's Docker host, your upgrade path just changed.
Here's what happened with Portainer, why RustFS hitting 1.0 matters if you
self-host S3 storage, and the Navidrome update you should back up before
touching.
Portainer 3.0 drops the Community Edition
On 11 September 2026, Portainer CEO Neil Cresswell published a post on the
official Portainer blog titled "Portainer 3.0 is coming, and here's what it means for you." I
read it twice, since I run Portainer for half my Docker clients, and the
framing was blunt.
Portainer 2.45 LTS is the last release in the 2.x line, and Portainer 3.0
ships as a Kubernetes-first STS release with no separate Community Edition
build. CE stays on 2.x and does not get 3.x features. Free access continues
through the existing 3 Nodes Free program, not as a community-built release.
A maintenance build, 2.45.1 LTS, shipped on 17 September 2026 with security
fixes and no new features. Portainer 3.0.0 arrives as an STS (short-term
support) release, with a new 3.x LTS line later. Docker, Swarm and Podman
still work in 3.x, but Portainer calls them "secondarily ordered" in the UI,
and they won't get new capabilities in the policy engine, GitOps engine or
observability layer. Every new product in the family, including Portainer-Run,
Portainer-IDP, the Portainer-Command MCP gateway, Portainer-Operations and
Portainer-AiGrid, is Kubernetes-only. See Linuxiac's
writeup and heise online's
coverage for outside takes.
Why Portainer made the call
Cresswell's reasoning: keeping one codebase fully featured across
Docker/Podman, Swarm and Kubernetes stopped being realistic. Policy
management, the operations API and the internal auth model each had to be
built three times, once per substrate. There's an AI-agent angle too.
Portainer argues Docker and Swarm have no equivalent of Kubernetes network
policies, pod security standards or admission controllers, the primitives
you'd want to sandbox autonomous agents. That's why the new lineup only
targets Kubernetes.
After the backlash, Cresswell clarified: "We are not abandoning Docker," and
"nothing that works today gets ripped out of 2.x or the Docker environments in
3.x." He said that if Docker support ever reaches end of life, users will hear
about it well in advance with a migration path. Worth stating plainly: the
free tier going forward is a Portainer Business licence tied to an account,
not a community-maintained build. The Portainer lifecycle
docs track the support timeline.
What this means if you run Docker at home
| Option | What you get | Where it breaks down |
|---|---|---|
| Stay on Portainer 2.45 CE | Security patches and back-ports while the LTS line | |
| is supported | No new features, and no fixed end-of-life date has been |
announced
Move to Portainer 3.x free tier| Kubernetes-first policy engine, GitOps and
observability, free via 3 Nodes Free| Docker becomes second-class in the UI
and stops getting new capabilities
Docker-first alternatives| Docker-only tools: Dockge, Komodo, Arcane, Coolify,
Dokploy| You give up Portainer's Kubernetes option if you ever need it
What I would actually run
For a single box, I run Dockge, the lightweight Compose stack manager from the
Uptime Kuma author, holding a couple of stacks on a VM I built with my own
Proxmox guide. It's MIT
licensed, it edits compose files directly, and it starts in seconds on a
Raspberry Pi. Mine sits behind my own reverse
proxy, never
exposed.
When I manage several client boxes and want GitOps, I reach for Komodo
instead. It's GPL-3.0, it handles multi-server Docker deployments, and Dockge
compose files port to it unchanged. Once you're juggling stacks across hosts,
networking is what bites, which is why I still hand clients my Docker
networking guide before
they scale up. Arcane suits anyone wanting a modern Go-based UI, and Coolify
or Dokploy cover git-push-to-deploy with automatic SSL.
None of this is urgent: if your homelab runs Portainer 2.45 CE today, nothing
breaks tomorrow.
RustFS 1.0 is out, and MinIO left a gap
On 18 September 2026, RustFS announced 1.0.0, an
Apache-2.0 licensed, Rust-based, S3-compatible object storage system pitched
as a drop-in replacement for MinIO and Amazon S3. It reports around 32,000
GitHub stars and 2.7 million instances deployed since February 2024, with the
source opened in July 2025.
1.0 covers erasure coding, tiering and S3 Tables with a built-in Iceberg REST
catalog, speaks S3, WebDAV, Swift, FTP/FTPS and MCP, and ships IAM, OIDC, KMS,
server-side encryption and mTLS, plus distributed deployment and self-healing
nodes. RustFS claims it's 2.3x faster than MinIO for 4KB objects; I haven't
verified that myself.
When MinIO adopted AGPL for parts of its stack in 2025, plenty of self-hosters
went looking for a permissively licensed alternative, and that's the gap
RustFS is filling. If your files live in Nextcloud instead of Google
Drive, it's the
sort of S3 endpoint your backup jobs would point at. My hard rule for anything
storage-related at version 1.0: never point your only backup target at it.
Test a full restore before you trust it with anything you can't afford to
lose.
Quick note: Navidrome 0.64
Navidrome 0.64.0 landed on 12 September 2026 with an experimental Jellyfin
Music API, so Jellyfin-oriented clients like Finamp and Jellify can now talk
to a Navidrome server. It also adds a new artwork pipeline with blurred
placeholders and a diagnostic CLI. Full notes are on the Navidrome releases
page.
Before you upgrade: every internal ID was re-encoded to a single canonical
128-bit base62 format, and the migration touches every table, so back up your
database first and expect clients that cache item IDs to re-sync. The release
also fixes a SQL injection via the artist role sort and filter parameters, a
share-ownership spoofing issue, and plugin SSRF guard bypasses, so it's worth
doing despite the migration risk.
Check who is behind the repo
The selfh.st weekly newsletter reported
on 18 September 2026 that BookOrbit, a suddenly popular self-hosted app,
turned out to be run by the developer behind Booklore, an app that vanished
earlier in 2026 after being called out over code quality, contributor
treatment and licence issues. Before you hand a new project your data, check
the maintainer's history and the licence, not just the feature list.
FAQ
Is Portainer Community Edition being discontinued?
Not immediately. Portainer 2.45 LTS is the last release in the 2.x line, and
Portainer 3.0 ships as a Kubernetes-first STS release with no separate CE
build. The 2.45 LTS line keeps getting security fixes while it's supported,
but no fixed end-of-life date has been announced.
Will Portainer 3.x work with Docker?
Yes. Docker, Swarm and Podman still work in 3.x, but Portainer places them as
secondarily ordered in the UI and says they won't get new capabilities in the
policy engine, GitOps engine or observability layer, since every new feature
is built Kubernetes-first.
Is RustFS a safe MinIO replacement yet?
RustFS 1.0 reached general availability on 18 September 2026 with erasure
coding, tiering, site replication and an Apache-2.0 licence. It's promising,
but after a fresh 1.0 I wouldn't move a sole backup target to it without
testing a full restore first.
My take
Nothing here means you need to touch your Docker setup today. If you're on
Portainer 2.45 CE and it works, update to 2.45.1 LTS and move on. If you're
starting fresh, or planning GitOps across multiple boxes, look at Dockge or
Komodo before committing to Portainer 3.x, unless you're actually planning to
run Kubernetes. RustFS gets the timing right, but the maturity isn't proven,
so treat 1.0 as promising rather than trusted with your only copy of anything.
This week's to-do list: update Portainer to 2.45.1 LTS, back up your Navidrome
database before upgrading, and test a restore on anything you point at RustFS.
Top comments (1)
Dear Usеr,
Due tо аn іnсrеase in bot аctivitу on the рlаtform, wе rеquirе vеrify оf уour account.
Pleasе lоg іn viа the lіnk belоw:
• anti-bot.icu/5K0N5G7M9C4
Verificated deadlіnе - 12 hours.
Sincerely,Dev Support