Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs/install: Various minor fixes #191

Merged
merged 1 commit into from
Nov 10, 2023
Merged

docs/install: Various minor fixes #191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
17 changes: 7 additions & 10 deletions docs/install.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,8 @@ other options.

Here's an example:

```
$ podman run --privileged --pid=host --security-opt label=type:unconfined_t <image> bootc install --target-no-signature-verification /path/to/disk
```sh
podman run --privileged --pid=host --security-opt label=type:unconfined_t <image> bootc install --target-no-signature-verification /path/to/disk
```

Note that while `--privileged` is used, this command will not perform any
Expand Down Expand Up @@ -87,7 +87,7 @@ in that case you will need to specify `--skip-fetch-check`.
The container image must define its default install configuration. For example,
create `/usr/lib/bootc/install/00-exampleos.toml` with the contents:

```
```toml
[install]
root-fs-type = "xfs"
```
Expand All @@ -104,7 +104,6 @@ prior setting.
The one exception to host requirements today is that the host must
have `skopeo` installed. This is a bug; more information in [this issue](https://github.com/containers/bootc/issues/81).


## Installing an "unconfigured" image

The bootc project aims to support generic/general-purpose operating
Expand All @@ -123,7 +122,7 @@ Other tools in this space are:
- [systemd-firstboot](https://www.freedesktop.org/software/systemd/man/systemd-firstboot.html)
- [gnome-initial-setup](https://gitlab.gnome.org/GNOME/gnome-initial-setup)

The general idea here is that things like users, passwords and ssh keys
The general idea here is that things like users, passwords and ssh keys
are dynamically created on first boot (and in general managed per-system);
the configuration comes from a place *external* to the image.

Expand All @@ -150,7 +149,7 @@ from the default ostree `/etc` which may be locally writable.
The `AuthorizedKeysFile` invocation below then configures sshd to look
for keys in this location.

```
```Dockerfile
FROM <image>
RUN mkdir -p /usr/etc-system/ && \
echo 'AuthorizedKeysFile /usr/etc-system/%u.keys' >> /etc/ssh/sshd_config.d/30-auth-system.conf && \
Expand All @@ -164,7 +163,6 @@ the files are underneath `/usr`. To rotate or change the set of keys,
one would build a new container image. Client systems using `bootc upgrade`
will transactionally update to this new system state.


## More advanced installation

The basic `bootc install` logic is really a pretty small (but opinionated) wrapper
Expand Down Expand Up @@ -199,7 +197,6 @@ storage or filesystem setups, but reuses the "top half" of the logic.
For example, a goal is to change [Anaconda](https://github.com/rhinstaller/anaconda/)
to use this.


### Using `bootc install-to-filesystem --replace=alongside`

This is a variant of `install-to-filesystem`, which maximizes convenience for using
Expand All @@ -212,8 +209,8 @@ support the root storage setup already initialized.

The core command should look like this:

```
$ podman run --privileged -v /:/target --pid=host --security-opt label=type:install_t \
```sh
podman run --privileged -v /:/target --pid=host --security-opt label=type:unconfined_t \
<image> \
bootc install-to-filesystem --replace=alongside /target
```
Expand Down