1
0
mirror of https://github.com/containers/bootc.git synced 2026-02-05 15:45:53 +01:00
Colin Walters 527151969a tree: Add missing -v /dev:/dev in a few places
We're really going to need to switch over to having the container
do dynamic mounts; cc https://github.com/containers/bootc/issues/380#issuecomment-1983721453

Just noticed this missing in one place, and found others with
a grep.

Right now we do operate without, but it can be racier.

Signed-off-by: Colin Walters <walters@verbum.org>
2024-06-22 09:21:25 -04:00
2023-10-20 09:05:23 -04:00
2024-03-06 17:10:43 +08:00
2024-02-08 17:56:47 -05:00
2023-12-01 16:50:44 -05:00
2024-05-17 14:35:13 +03:00

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

NOTE: At the current time, bootc has not reached 1.0, and it is possible that some APIs and CLIs may change.

Documentation

See the project documentation; there are also operating systems and distributions using bootc; here are some examples:

Developing bootc

Are you interested in working on bootc? Great! See our HACKING.md guide.

Description
Boot and upgrade via container images
Readme 22 MiB
Languages
Rust 92.7%
Nushell 3%
Shell 2.2%
Just 0.6%
Dockerfile 0.5%
Other 1%