1
0
mirror of https://github.com/containers/bootc.git synced 2026-02-05 15:45:53 +01:00
Steven Presti 858acbe5dd cli: add container lint
Add an entrypoint that basically everyone can start
adding to their builds which performs some basic
static analysis for known problems.

Closes : #216

Co-authored-by: Joseph Marrero <jmarrero@redhat.com>
Co-authored-by: Huijing Hei <hhei@redhat.com>
Co-authored-by: Yasmin de Souza <ydesouza@redhat.com>

Signed-off-by: Steven Presti <spresti@redhat.com>
Signed-off-by: Colin Walters <walters@verbum.org>
2024-05-30 19:52:46 -04:00
2023-10-20 09:05:23 -04:00
2024-03-06 17:10:43 +08:00
2024-05-30 19:52:46 -04:00
2024-05-30 19:52:46 -04:00
2024-05-30 19:52:46 -04:00
2024-05-24 10:09:03 +08:00
2024-05-24 10:09:03 +08:00
2024-02-08 17:56:47 -05:00
2023-12-01 16:50:44 -05:00
2024-05-09 13:18:37 -06: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.

Status

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

More information

See the project documentation.

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%