We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
tier-0
tier-1
bootupd
bootc
rpm-ostree
bootc status
dnf5
osbuild-composer
See:
The text was updated successfully, but these errors were encountered:
registry.fedoraproject.org/fedora-bootc
Those are the bootc ones. Don't you want to have IoT dedicated ones?
Sorry, something went wrong.
registry.fedoraproject.org/fedora-bootc Those are the bootc ones. Don't you want to have IoT dedicated ones?
Yes, covered a little further down:
Fedora IoT derived bootc image is defined and composed automatically
Does this issue effectively replace #38?
failed to write bootloader configuation
For broader awareness, I filed an issue in the Fedora bootc project about the size of the base image - https://gitlab.com/fedora/bootc/tracker/-/issues/36
No branches or pull requests
Notes
Roadmap
Building and publishing Bootable Container images
tier-0
container and atier-1
containers as a part of the Fedora IoT compose process.tier-1
images are published to:bootupd integration
bootupd
in the IoT composebootc integration
bootc
in the IoT composerpm-ostree
until all issues resolvedbootc status
does not report unlocked status containers/bootc#474DNF5 integration
dnf5
in the IoT compose:Switching to Bootable Container images
Local package layering
Rebasing on Fedora Bootc manifests
Rebasing on Fedora Bootc container images
Osbuild
osbuild-composer
for IoT deliverablesDocumentation updates
References
See:
The text was updated successfully, but these errors were encountered: