bootc · OCI · deterministic
The desktop
is compiled.
Declared intent becomes a typed plan and a bootable image. Same inputs, same artifact.
01 Compile
YAML in.
One image out.
You describe the machine; DeskOS checks it, merges the layers and writes a generated Containerfile. That file is the whole output: read it, diff it, build it with podman. There is no runtime, no agent and no controller.
deterministic · offline · no scripts · nothing runs on the machine
02 Platforms
Same intent, the vendor's base.
Each platform starts from its own vendor's bootc image — never a derived one — and says what has actually been verified on it. What is not measured is written as not measured.
| Platform | Base | Composes | Image | Booted | Published |
|---|---|---|---|---|---|
| CentOS Stream 10 | centos-bootc | validated | CI | GNOME + session | quay.io/deskos |
| Fedora 45 | fedora-silverblue | validated | CI | GNOME + session | quay.io/deskos |
| AlmaLinux 10 | almalinux-bootc | validated | CI | GNOME + session | quay.io/deskos |
| RHEL 10 | rhel-bootc | validated | your build | your hardware | never |
RHEL-derived images are never published. CentOS Stream 10 and Fedora 45 publish a signed installer ISO; AlmaLinux 10 publishes an image only.
03 Install
Install once.
Update as an image.
The community images are published as bootable containers. Write one to a disk, boot it, and every later update is a new image staged beside the old one — the previous one stays one boot away.
Two installers are published, both built from a published image and
mirrored with a checksum at download.deskos.org:
CentOS Stream 10, installed and booted in a VM before release, and
Fedora 45, where a test-only ISO from the same image installed
unattended and reached the installed system. The published Fedora ISO asks for the
disk and LUKS, so it is the person installing who finishes it.
AlmaLinux 10 publishes a bootc image you write a disk from with
bootc-image-builder; Core publishes no installer ISO for it.
Download the CS10 ISO Download the Fedora 45 ISO
Before you boot it, check the checksum and the signature: verify a download.
04 Questions
Before you ask.
Is this a distribution?
No. DeskOS compiles workstations onto the base each vendor already ships. It does not own a kernel, a package archive or a support contract for one.
Does anything of DeskOS run on the machine?
No. DeskOS writes a Containerfile; podman builds it; bootc boots the image. The optional
deskos companion only reports what the image contains.
What does “deterministic” mean?
Same resources, same plan and same Containerfile. The image build is not bit-for-bit reproducible yet, because external repositories move — and the docs say so.
Where are the ISOs?
Both are on download.deskos.org:
CentOS Stream 10 first, then Fedora 45, each with its checksum and the dated
build behind the stable name. AlmaLinux 10 publishes an image only,
and RHEL ISOs are never published.