Skip to content

Drop Docker Engine; keep Compose for podman compose - #196

Merged
TB516 merged 1 commit into
mainfrom
drop-docker-engine
Nov 18, 2026
Merged

TB516 merged 1 commit into
mainfrom
drop-docker-engine

Conversation

@TB516

@TB516 TB516 commented Nov 18, 2026

Copy link
Copy Markdown
Owner

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 docker group and a firewalld patch just for it. The one piece Podman still leans on is Compose, since podman compose hands off to Docker Compose.

The image now ships only Docker Compose, from Docker's official compose-bin image at the same v5.7.0 we ship today (byte-identical binary). It lives at /usr/libexec/docker/cli-plugins/docker-compose, which podman compose checks on its own, so it stays off PATH. Compose talks to Podman through its API socket, which nothing enabled before, so podman.socket is now enabled for every user through the existing user preset.

Dropped with the engine:

  • core/docker.bst and 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-bin instead of docker.io/library/docker.

Once this lands, /var/lib/docker and the docker group 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 --build built an image, published a port and mounted a named volume. Rootful Podman kept its published port across firewall-cmd --reload. The Flathub Zed (v1.28.1) with "use_podman": true opened a compose-based dev container (built app plus Postgres), and its terminal ran inside the container and queried the db service.

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.
@TB516
TB516 merged commit 5695fd3 into main Nov 18, 2026
1 check passed
@TB516
TB516 deleted the drop-docker-engine branch November 18, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant