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

README: provide an example to generate a booting image #282

Closed
wants to merge 1 commit into from
Closed

README: provide an example to generate a booting image #282

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,18 @@ 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.

# Example

To try bootc today run:
```
$ truncate -s 10G test-disk.img
$ sudo losetup -Pf test-disk.img
$ LOOP=$(sudo losetup | grep test-disk.img | cut -f1 -d' ')
$ sudo podman run --rm --privileged --pid=host --security-opt label=type:unconfined_t quay.io/centos-bootc/fedora-bootc:eln bootc install to-disk --generic-machine "$LOOP"
$ qemu-system-x86_64 -m 1500 -snapshot -accel kvm -cpu host -bios /usr/share/OVMF/OVMF_CODE.fd ./test-disk.img
```


# More information

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