No description
Find a file
2025-08-18 23:45:01 -07:00
deb-bootc-compose@57bb8aafbe first commit 2025-08-18 23:45:01 -07:00
dev-architecture-docs first commit 2025-08-18 23:45:01 -07:00
inspiration first commit 2025-08-18 23:45:01 -07:00
internal first commit 2025-08-18 23:45:01 -07:00
parallel_projects first commit 2025-08-18 23:45:01 -07:00
test-output/minimal/amd64/container-build first commit 2025-08-18 23:45:01 -07:00
.gitignore first commit 2025-08-18 23:45:01 -07:00
demo_current_capabilities.py first commit 2025-08-18 23:45:01 -07:00
developmental-roadmap.md first commit 2025-08-18 23:45:01 -07:00
integration_test.py first commit 2025-08-18 23:45:01 -07:00
readme.md first commit 2025-08-18 23:45:01 -07:00
README.md first commit 2025-08-18 23:45:01 -07:00
TESTING.md first commit 2025-08-18 23:45:01 -07:00
TODO.md first commit 2025-08-18 23:45:01 -07:00

Debian Bootc Ecosystem

Overview

This project creates Debian's complete bootc ecosystem - three foundational tools that work together to create Debian bootc images. This is Debian's answer to Fedora's Pungi-Koji-Mock ecosystem, designed to support Debian Atomic, Particle-OS, and other Debian bootc variants.

The Three Tools Working Together

┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│ deb-bootc-      │    │ deb-orchestrator│    │    deb-mock     │
│   compose       │    │   (Koji equiv)  │    │   (Mock equiv)  │
│ (Pungi equiv)   │    │                 │    │                 │
└─────────────────┘    └─────────────────┘    └─────────────────┘
         │                       │                       │
         │ 1. "I need packages" │                       │
         │──────────────────────▶│                       │
         │                       │                       │
         │                       │ 2. "Build this .deb" │
         │                       │──────────────────────▶│
         │                       │                       │
         │                       │ 3. "Environment ready"│
         │                       │◀──────────────────────│
         │                       │                       │
         │                       │ 4. "Build complete"   │
         │                       │◀──────────────────────│
         │                       │                       │
         │ 5. "Packages ready"   │                       │
         │◀──────────────────────│                       │

How the Tools Work Together

1. deb-bootc-compose (Pungi Equivalent)

  • Role: Main orchestrator for Debian bootc image creation
  • Purpose: Coordinates the entire compose process
  • What it does: Manages image composition, OSTree creation, container generation

2. deb-orchestrator (Koji Equivalent)

  • Role: Distributed build orchestration system
  • Purpose: Manages package building at scale
  • What it does: Coordinates builds across multiple builder hosts, manages build tasks

3. deb-mock (Mock Equivalent)

  • Role: Chroot build environment manager
  • Purpose: Creates isolated build environments
  • What it does: Provides clean, reproducible chroot environments for package building

The Workflow

  1. deb-bootc-compose needs packages for image creation
  2. deb-orchestrator receives build requests and coordinates package building
  3. deb-mock provides isolated build environments on each builder
  4. deb-orchestrator executes builds in deb-mock-managed environments
  5. deb-bootc-compose receives completed packages for image composition

Development Status

  • Status: Foundation development (Phase 1)
  • Timeline: Parallel development of all three tools
  • Goal: Complete Debian bootc ecosystem in 18 months

Getting Started

See the parallel_projects directory for detailed information about each tool and the parallel development approach.