https://github.com/containers/bootc

Boot and upgrade via container images
https://github.com/containers/bootc

Last synced: 3 days ago
JSON representation

Boot and upgrade via container images

• Host: GitHub
• URL: https://github.com/containers/bootc
• Owner: containers
• License: apache-2.0
• Created: 2022-11-30T20:11:04.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2024-10-23T20:02:10.000Z (11 days ago)
• Last Synced: 2024-10-25T02:24:39.421Z (10 days ago)
• Language: Rust
• Homepage: https://containers.github.io/bootc/
• Size: 1.56 MB
• Stars: 651
• Watchers: 25
• Forks: 77
• Open Issues: 87
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE-APACHE

Awesome Lists containing this project

• awesome - containers/bootc - Boot and upgrade via container images (others)
• awesome_atomic - BootC - Transactional, in-place operating system updates using OCI/Docker container images. (Experimental) (Lower level tools)
• awesome-starred - containers/bootc - Boot and upgrade via container images (others)

README

        
![bootc logo](https://raw.githubusercontent.com/containers/common/main/logos/bootc-logo-full-vert.png)

# bootc

Transactional, in-place operating system updates using OCI/Docker container images.

## Motivation

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.

## Status

The CLI and API are considered stable. We will ensure that every existing system

can be upgraded in place seamlessly across any future changes.

## Documentation

See the [project documentation](https://containers.github.io/bootc/).

## Adopters (base and end-user images)

The bootc CLI is just a client system; it is not tied to any particular

operating system or Linux distribution. You very likely want to actually

start by looking at [ADOPTERS.md](ADOPTERS.md).

## Community discussion

The [Github discussion forum](https://github.com/containers/bootc/discussions) is enabled.

This project is also tightly related to the previously mentioned Fedora/CentOS bootc project,

and many developers monitor the relevant discussion forums there. In particular there's a

Matrix channel and a weekly video call meeting for example: .

## Developing bootc

Are you interested in working on bootc?  Great!  See our [CONTRIBUTING.md](CONTRIBUTING.md) guide.

There is also a list of [MAINTAINERS.md](MAINTAINERS.md).