Skip to content
@DaemonCores

DaemonCores

DaemonCores

DaemonCores Banner

Foundations for immutable, Debian-based distributions. Documentation Community Debian Bootc

Bring the atomic operating-system model to the Debian ecosystem, server side included.


DaemonCores

DaemonCores wants to foster an ecosystem of immutable Linux distributions based on Debian. It does not build one final distribution: it builds a reusable foundation, Debian bootc, on which teams and communities can build their own specialised bootc/OSTree systems, with the shared CI that builds, tests, signs and publishes them. Its distinctive angle is access to the Debian ecosystem, particularly on the server side, for software that already lives on Debian and APT.

Everything is at an early stage: Debian bootc is a Developer Alpha, its CI/CD is being debugged and no working installer ISO is available yet. Repository status is documented explicitly rather than implied by the organization name.

Projects

Repository Role Status
debian-bootc The foundation: Debian 13 bootc/OSTree base image (blank template, no GUI), custom Debian packages, boot tests Developer Alpha; CI/CD being debugged
DaemonCores-VE Server example: transactional Proxmox VE image built on debian-bootc Active development, depends on the base being repaired
DaemonCores-CI Reusable GitHub Actions workflows and composite actions shared by the image repositories Under repair
DaemonCores-Phone Separate early proof of concept (phone system tooling) Very early, not a product
AlmaBuilder Small AlmaLinux bootc image and net-install ISO reference Prototype

What exists in the repositories

  • Debian packages for bootc, OSTree, composefs, bootupd, the boot stack, first-boot setup, and project-specific host services.
  • OCI image builds with architecture-specific jobs, image signing, content-aware rebuilds, and multi-architecture manifest publication.
  • QEMU/KVM boot tests that install an image onto a virtual disk and validate the running system over SSH before publication.
  • Installer ISO generation (the ISOs currently on the Releases are known to be broken).
  • A Proxmox VE layer with bootc-aware networking, storage, firewall, memory, power, cooling, and container tooling.
  • A reusable, manifest-driven package and image pipeline shared across repositories.

Engineering model

The operating system is treated as a versioned image rather than a host assembled by repeated in-place package operations:

  1. source packages and project overlays are built into signed Debian repositories;
  2. a Containerfile assembles the operating-system image;
  3. the image is installed and booted under QEMU for runtime validation;
  4. successful builds are published to GHCR and signed;
  5. installer artifacts are produced from the published image.

The individual repositories document their supported paths, current limitations, build inputs, and required credentials. Interfaces that are still being validated are labelled as such instead of being presented as released functionality.

Contributing

Issues and pull requests are welcome. For changes that affect image format, package manifests, boot behaviour, or shared CI interfaces, open an issue first so the design can be discussed across the affected repositories.

Security reports should follow the private reporting process described in the organization-wide SECURITY.md.


Made with ⭐ by the DaemonCores community Documentation Community Debian Bootc

Pinned Loading

  1. .github .github Public

Repositories

Showing 9 of 9 repositories

Top languages

Loading…

Most used topics

Loading…