You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This site is built using [Zola](https://www.getzola.org/), a static site generator built with Rust. The theme is [Juice](https://www.getzola.org/themes/juice/).
- Juice [Installation info](https://juice.huhu.io/#installation) - Note that I've explicitly dropped the git history and VCS info from the theme directory.
6
+
7
+
Under the hood, Zola uses [Tera](https://keats.github.io/tera/) for templating.
8
+
9
+
## Structure
10
+
11
+
The site lives in the `site` directory. Content like pages or blog posts live in, appropriately, `content`. Any kind of image like screenshots would live in `static`.
12
+
13
+
The `templates` directory extends elements from the theme, which is stored in, appropriately, `themes/juice`.
14
+
15
+
## Building
16
+
17
+
Once you've installed Zola, proceed as follows:
18
+
19
+
```bash
20
+
cd site
21
+
zola serve
22
+
```
23
+
24
+
Go to the URL for the webserver (likely `localhost:1111`) to explore the site.
25
+
26
+
You can also use `zola build` to build it once to the `public` directory if you so choose.
Transactional, in-place operating system updates using OCI/Docker container images.
6
+
7
+
## Motivation
8
+
9
+
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.
10
+
11
+
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.
12
+
13
+
## Status
14
+
15
+
The CLI and API are considered stable. We will ensure that every existing system can be upgraded in place seamlessly across any future changes.
16
+
17
+
## Documentation
18
+
19
+
The project documentation is hosted on a different site: [Docs](https://bootc-dev.github.io/bootc/)
20
+
21
+
## Versioning
22
+
23
+
Although bootc is not released to crates.io as a library, version numbers are expected to follow [semantic versioning](https://semver.org/) standards. This practice began with the release of version 1.2.0; versions prior may not adhere strictly to semver standards.
24
+
25
+
## Adopters (base and end-user images)
26
+
27
+
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](about/adopters).
28
+
29
+
## Community discussion
30
+
31
+
-[Github discussion forum](https://github.com/containers/bootc/discussions) for async discussion
32
+
-[#bootc-dev on CNCF Slack](https://cloud-native.slack.com/archives/C08SKSQKG1L) for live chat
33
+
- Recurring live meeting hosted on [CNCF Zoom](https://zoom-lfx.platform.linuxfoundation.org/meeting/96540875093?password=7889708d-c520-4565-90d3-ce9e253a1f65) each Friday at 15:30 UTC.
34
+
-[Meeting notes on HackMD](https://hackmd.io/@cgwalters/HJk3Aj0ree/edit)
35
+
36
+
This project is also currently 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 chat meeting; [learn more](https://docs.fedoraproject.org/en-US/bootc/community/).
37
+
38
+
## Developing bootc
39
+
40
+
Are you interested in working on bootc? Great! Reference our [contribution guide](about/contributing).
41
+
There is also a list of [Maintainers](about/maintainers).
42
+
43
+
## Governance
44
+
Reference [Governance](about/governance) for project governance details.
45
+
46
+
## Badges
47
+
48
+
[](https://www.bestpractices.dev/projects/10113)
49
+
50
+
### Code of Conduct
51
+
52
+
The bootc project is a [Cloud Native Computing Foundation (CNCF) Sandbox project](https://www.cncf.io/sandbox-projects/) and adheres to the [CNCF Community Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
53
+
54
+
---
55
+
The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/trademark-usage/).
Imagine the ability to set up your operating system using a file you can check into source control. bootc basically turns your operating system into a containerized system, complete with in-place updates, custom configurations and pre-installed software and drivers, and more. You can share your custom containerized operating system image with others, too.
11
+
12
+
Unlock the power of bootc with shared custom OS images.
0 commit comments