bootc-dev/bootc
Boot and upgrade via container images
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 4 days ago, with 108 contributors on GitHub.
Gained 17% fewer stars in the last 90 days than in the 90 days before.
Use Cases & Benefits
- Enables transactional, in-place operating system updates using OCI/Docker container images.
- Provides seamless OS upgrades by leveraging container image layering for reliable and atomic system updates.
- Use for upgrading Linux host systems without rebooting into a containerized environment.
- Ideal for maintaining consistent base OS images across diverse Linux distributions using standard container formats.
- Use for integrating container-based OS updates into automated CI/CD pipelines for infrastructure management.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Other
GitHub could not identify this license; read the LICENSE file before depending on it.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
- License not identified by GitHub; read the LICENSE file before depending on it.
General guidance from repository metadata, not legal advice. How we score
From the README
Transactional, in-place operating system updates using OCI/Docker container images.
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.
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. More about this in the docs; see below.The CLI and API are considered stable. We will ensure that every existing system can be upgraded in place seamlessly across any future changes.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
240+25
Open issues
374+64
Compared with peers in DevOps
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| milind-soni/OpenMausBot | 13.5K | +6.0K | 45 | today |
| DuarteSantos8/openGym | 19.7K | +2.4K | 60 | 2 days ago |
| AstrBotDevs/AstrBot | 46.2K | +1.4K | 65 | 5 days ago |
| elie222/rakazo | 7.2K | +922 | 59 | 26 days ago |
| superplanehq/superplane | 8.8K | +435 | 60 | 7 days ago |
| bootc-dev/bootc | 2.3K | — | 65 | 4 days ago |
| Category median | 13.5K | +1.4K | 60 | — |
Discover Repositories
Search across tracked repositories by name or description