Debian Stable vs Arch on a Homelab: Rolling Release That Breaks Compose Overnight

Tobias Keller

Tobias Keller

September 18, 2026

Debian Stable vs Arch on a Homelab: Rolling Release That Breaks Compose Overnight

Arch on a homelab feels like competence. You pacman -Syu on a Sunday, you get the kernel the internet is talking about, and Docker Compose still comes up — until a Monday when it does not. The container runtime moved. The iptables backend became nft and your published ports are theatre. A NVIDIA container toolkit wanted a driver you did not pin. Immich starts, then the database volume is fine and the proxy is a 502 because the host’s docker package and the compose plugin had a one-night stand.

Debian Stable is the opposite mood. You install Bookworm or Trixie, you enable backports only when you must, and you live with a container engine that is “old” in Discord and current enough to run the same compose file for two years. The tax is not excitement. The tax is a kernel that does not know your new USB NIC until you decide you care.

I keep Chezmoi across a Mac mini, a Debian NAS, and a Pi that should not have a prompt. The NAS is Debian because I have already paid the Arch tax on a box that held the family photos. I will run Arch on a toy. I will not roll the host that is allowed to break compose overnight.

What actually broke when I rolled the host

The compose file did not change. That is the insult. YAML you have not touched is not a guarantee the host’s Docker, containerd, runc, cgroup layout, and firewall still agree.

The failures I have cleaned up, mine and other people’s:

  • docker-compose versus the plugin. Arch will happily leave you with a docker compose that is not the binary your systemd unit calls. A timer runs docker-compose pull and fails silent. The stack is “up” on stale images until you look.
  • iptables-nft and published ports. A host firewall update plus Docker’s chain rewriting equals “the container is healthy and unreachable.” Uptime Kuma on the same host still says 200 because it talks over the Docker bridge. The living room cannot.
  • Kernel plus ZFS plus containers. DKMS rebuild at 2 a.m., pool mounts late, compose starts early, bind mounts are empty directories, and now you have a new empty Postgres that looks initialized. This one deserves a drink and a snapshot policy.
  • Python on the host. You should not have host Python in the critical path. Someone always does: a backup script, a Certbot hook, a tiny API. Arch moves Python. The venv dies. The hook dies. The cert dies three weeks later.
  • NVIDIA and Hailo and Coral. Vendor stacks assume a driver cadence. Rolling the kernel because you were bored is how a Frigate box becomes a CPU detector overnight.

Debian Stable will still surprise you — a point release, a backported kernel you installed yourself — but the surprise is scheduled. Arch’s surprise is the default.

Homelab machine with Docker stacks and a terminal, basement light

The case for Arch anyway

If the box is a workstation that also runs a few containers, Arch is pleasant. New Mesa, new kernel, new podman, you are at the desk to see the smoke. If the box is a lab for learning systemd and you have backups you have restored this month, roll it. I am not a scold about Arch. I am a scold about Arch as the silent appliance under the TV.

Arch’s wiki is still the best operations document in the consumer Unix world. When something breaks, you will find the paragraph. Debian’s documentation will be correct and older than your error. That difference is why people stay on Arch after the first compose outage. They like being able to read.

AUR is the other gravity. You want a package that Debian will not see for a year. You install it. You now have a trust story and a rebuild story. Fine on a laptop. On the NAS it is how an unattended upgrade becomes a personality.

I will put Arch on a Beelink that I can wipe. I will put it on a VM whose job is “try the new Forgejo.” I will not put it on the only host that speaks to the USB backup disk.

The case for Debian, including the boring parts

Debian Stable plus Docker from Debian’s packages is older than Docker’s own repo. Debian Stable plus Docker’s official repo is a common homelab pattern and a smaller roll than full Arch. You get newer engine, older everything else. That hybrid is how I run the NAS: host is Stable, engine is pinned from a known source, compose files are the moving part.

The moving part should be the images, not the host. Pin image digests if you are serious. Pin them if you have been burned. I pin the ones that hold data. I float the ones I can recreate. Debian makes that discipline easier because the host is not also floating underneath.

backports exist. Use them for a NIC or a kernel, not as a lifestyle. The lifestyle is how Debian becomes a worse Arch with less wiki.

Unattended-upgrades on Debian is a choice. I enable security updates. I do not enable “reboot into a new kernel at 4 a.m. without me” on a host that mounts encrypted disks by a passphrase on a USB key I have to be home for. Arch users who enable a weekly pacman -Syu in cron have built the same trap with more packages in the diff.

Server closet with labeled machines, one with a sticky note, cool light

Compose is not a distro, but it sits on one

People say “I only run Docker, the distro does not matter.” Then they need:

  • a kernel module for a Coral or a GPU
  • a host mount for Time Machine or SMB
  • a host Caddy or a host WireGuard because they did not want that in compose
  • a backup agent that is not a container
  • udev rules for a Zigbee stick that moves from ttyUSB0 to ttyUSB1 after a kernel update

That is a distro. Compose rides on it. When the stick moves, Home Assistant is “up” and the mesh is empty. When the SMB module changes, the living room TV cannot see the share and Jellyfin is still green. You will debug the container. The bug is the host.

Debian’s slower udev and kernel story has saved me more hours than Arch’s newer docker has given me. I can pull a new Immich image on Debian tomorrow without also pulling a new world.

A third option people skip

Proxmox on Debian, guests as whatever. The hypervisor stays Stable. The app VM can be Arch if you insist. A broken roll is a rollback of a VMID, not a night with a live USB on the floor. I still keep the NAS-ish workload close to metal or a single Debian VM because I am tired of nested storage tricks. The point stands: if you want to roll something, roll a guest.

Immutable hosts — Fedora CoreOS, openSUSE MicroOS — are the other “stop rolling the package soup” answer. They are not this article. They are the right next question if both Debian and Arch feel like the wrong granularity.

How I choose for a new box

If it holds irreplaceable data or is the only ingress, Debian Stable. If it is a scratch builder or a desktop I sit at, Arch or the desktop I already like. If someone else has to SSH in when I am away, Debian, because I can tell them the version number and they can find a page that matches.

If you are already on Arch and compose is fine, I will not convert you for sport. I will ask whether last month’s pacman log is something you read. If you do not read it, you are already taking the overnight risk. Put the risk on a VM or take Debian the next time the box dies for a reason that was not your YAML.

I used to administer campus Linux labs. The machines that survived break weeks were the ones that did not surprise the people with the on-call phone. A homelab is a lab with worse documentation and a sleeping family. Rolling release is a joy when you are awake and at the keyboard. It is a personality defect when it is how the photo library meets Monday.

What I tell people after the outage

Restore first. Then look at whether the host or the image moved. If the host moved, write it down. If you stay on Arch, pin the docker stack packages or stop unattended rolling. If you migrate to Debian, migrate on a Saturday with a disk you can fail. Do not migrate in the thread where compose is still down.

Debian Stable versus Arch is not a purity fight. It is whether the host is allowed to be the release channel. Compose already is a release channel — every latest tag you did not pin. Two rolling layers is how you get an overnight you cannot bisect. Pick one layer to be boring. I pick the host. I have the Chezmoi repo to prove I like control elsewhere. The NAS does not need to be interesting. It needs to still be a NAS after a Sunday update I thought was harmless.

More articles for you