Repository navigation
Drop Docker Engine; keep Compose for podman compose - #196
Merged
Merged
Conversation
Podman is now the only container engine. Docker Compose comes from the official compose-bin image and sits in the cli-plugins path that podman compose checks, so it stays off PATH. podman.socket is enabled for every user because Compose talks to Podman through that API. The firewalld iptables patch only existed for Docker's iptables backend, so it goes too.
This was referenced Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'd stopped needing Docker: every project I use it for works with Podman, and the image was carrying a second root daemon, its runtime helpers, a
dockergroup and a firewalld patch just for it. The one piece Podman still leans on is Compose, sincepodman composehands off to Docker Compose.The image now ships only Docker Compose, from Docker's official
compose-binimage at the same v5.7.0 we ship today (byte-identical binary). It lives at/usr/libexec/docker/cli-plugins/docker-compose, whichpodman composechecks on its own, so it stays off PATH. Compose talks to Podman through its API socket, which nothing enabled before, sopodman.socketis now enabled for every user through the existing user preset.Dropped with the engine:
core/docker.bstand its service, sysusers and daemon config.patches/dakota/firewalld-iptables.patch, which only existed for Docker's iptables backend.Renovate now tracks
docker.io/docker/compose-bininstead ofdocker.io/library/docker.Once this lands,
/var/lib/dockerand thedockergroup stay on an installed system until removed by hand.Proof: built the image locally and upgraded a copy of the VM test disk from the current Docker image with
bootc switch/upgrade. It boots with no failed units and has no Docker binaries or units. As the desktop user,podman compose up --buildbuilt an image, published a port and mounted a named volume. Rootful Podman kept its published port acrossfirewall-cmd --reload. The Flathub Zed (v1.28.1) with"use_podman": trueopened a compose-based dev container (built app plus Postgres), and its terminal ran inside the container and queried thedbservice.