526f1c1afd
- Complete documentation for all bootc commands and subcommands - Debian-specific adaptations and workarounds - Manual installation methods to bypass bootc reliability issues - Technical guides with Rust source code analysis - Flowcharts and external command references - Hidden command documentation (bootc internals, state, etc.) - Composefs integration analysis - Base image creation guides (with and without bootc binary) - Management scripts and automation - Comprehensive troubleshooting and examples
27 lines
1.7 KiB
Markdown
27 lines
1.7 KiB
Markdown
# bootc for Debian
|
|
|
|
Transactional, in-place operating system updates using OCI/Docker container images. bootc is the key component in a broader mission of bootable containers for Debian systems.
|
|
|
|
The original Docker container model of using "layers" to model applications has been extremely successful. This project aims to apply the same technique for bootable host systems - using standard OCI/Docker containers as a transport and delivery format for base operating system updates on Debian.
|
|
|
|
The container image includes a Linux kernel (in e.g. `/usr/lib/modules`), which is used to boot. At runtime on a target system, the base userspace is _not_ itself running in a container by default. For example, assuming systemd is in use, systemd acts as pid1 as usual - there's no "outer" process.
|
|
|
|
## Status
|
|
|
|
The CLI and API for bootc are now considered stable. Every existing Debian system can be upgraded in place seamlessly across any future changes.
|
|
|
|
However, the core underlying code uses the ostree project which has been powering stable operating system updates for many years. The stability here generally refers to the surface APIs, not the underlying logic.
|
|
|
|
## Debian Integration
|
|
|
|
bootc for Debian leverages the existing Debian package management system (`apt`) and integrates with Debian's traditional update mechanisms while providing the benefits of container-based OS updates. This allows Debian systems to benefit from:
|
|
|
|
- Atomic updates with rollback capability
|
|
- Container-based OS image management
|
|
- Simplified system maintenance and deployment
|
|
- Integration with existing Debian infrastructure
|
|
|
|
---
|
|
|
|
The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see Trademark Usage.
|
|
|