-
Notifications
You must be signed in to change notification settings - Fork 107
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
Cloud API: Add Fedora IoT bootable container #3916
Cloud API: Add Fedora IoT bootable container #3916
Conversation
4019ec3
to
32d3dba
Compare
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.
❤️
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.
LGTM
32d3dba
to
1f5e09d
Compare
Missed a denylist test. Fixed. |
1f5e09d
to
8ac2a25
Compare
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.
❤️
9dbb0dc
to
b29e766
Compare
Cherry-picked the two commits from #3919 for CI fixage. |
The image type supports uploading to both s3 and container registries. Right now we only care about getting it in Koji, so let's just add it to the s3 upload section. The container registry test also embeds containers in the image, which the iot-bootable-container doesn't support (yet).
Required for bootc for iot-bootable-container.
We only want to build this image type in Fedora Koji.
b29e766
to
2c22104
Compare
Most CI failures are now related to an RHOS-01 outage. |
Add the Fedora iot-bootable-container to the cloud API and include it in the API tests.
See osbuild/images#361 for image definition introduction.
We don't intend to have this available in osbuild-composer on-prem (Weldr), so it's added to the deny list.
This pull request includes: