-
Notifications
You must be signed in to change notification settings - Fork 20
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.
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
Create bootc-setup.adoc #85
base: main
Are you sure you want to change the base?
Conversation
Create basic IoT bootc docs. More to come...
Since the launch of Fedora 41, Fedora IoT has supported bootable containers (bootc). | ||
Bootable containers are similar in function to other containers (like Podman), but allow the user to boot into the container as an immutable system. | ||
Any updates or package installs are then layered on top of the base bootc image, allowing rollbacks in the event of an issue. | ||
Each bootc image ships with a kernel, bootloader, drivers, etc, rendering them fully bootable and not requiring a container manager (Podman, Kubernetes, etc). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit weird, you would/could still use a container manager such as podman to maintain applications, the container in the bootc case is mechanism for maintaining the base OS.
|
||
== Installing/Layering Packages onto the Bootable Container | ||
|
||
Installing packages is the same as on an ostree Fedora IoT image and retains the same rpm-ostree functionality: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is incorrect, you use dnf.
Installing packages is the same as on an ostree Fedora IoT image and retains the same rpm-ostree functionality: | ||
|
||
---- | ||
sudo rpm-ostree install htop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to be updated.
sudo bootc switch registry.fedoraproject.com/fedora-iot:latest | ||
---- | ||
|
||
The following can be used to ensure the image has been downloaded and set for boot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put an example output here rather than saying "Look for XXX"
Also, check that the `rollbackQueued:` field shows `true`. | ||
|
||
---- | ||
sudo bootc status |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, put sample output.
Create basic IoT bootc docs. More to come...