cloud-image-uploader: update container image config for IoT changes #2580

Merged
ryanlerch merged 1 commit from ciu-iot-renames into main 2025-04-22 21:01:34 +00:00
Contributor

We finally merged https://pagure.io/fedora-iot/pungi-iot/pull-request/102
which changes the properties of the container images built in the
IoT compose. This should adjust to that and publish both the base
and IoT images, if we got it all right.

Signed-off-by: Adam Williamson awilliam@redhat.com

We finally merged https://pagure.io/fedora-iot/pungi-iot/pull-request/102 which changes the properties of the container images built in the IoT compose. This should adjust to that and publish both the base and IoT images, if we got it all right. Signed-off-by: Adam Williamson <awilliam@redhat.com>
First-time contributor
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/6de7dd7ee3d846e9b21f38715a24d30f - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/60cca1c466954569b7ae3033ac9ca26f) : SUCCESS in 2m 38s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/7c9e70aadf644b13a46c015aad822f86) : SUCCESS in 2m 14s
Author
Contributor

merging this now as the pungi-iot commit is already merged so we need to be in line with it. @pwhalen and I will keep an eye on the next compose and try to ensure it's all right.

merging this now as the pungi-iot commit is already merged so we need to be in line with it. @pwhalen and I will keep an eye on the next compose and try to ensure it's all right.
Author
Contributor

Pull-Request has been merged by adamwill

Pull-Request has been merged by adamwill
Contributor

Is this related to https://pagure.io/fedora-infrastructure/issue/12508 ? or is that a seperate thing?

Is this related to https://pagure.io/fedora-infrastructure/issue/12508 ? or is that a seperate thing?
Author
Contributor

um, I'm not entirely sure. if IoT is using bootc/image mode/whatever you want to call it by default now and what you get from rpm-ostree upgrade on IoT is based on pulling the images from quay.io / registry.fp.o , this may fix that, yeah. it should result in every IoT container image build getting synced to the registry, and the f42 ones should get the 'latest' tag.

um, I'm not entirely sure. if IoT is using bootc/image mode/whatever you want to call it by default now and what you get from `rpm-ostree upgrade` on IoT is based on pulling the images from quay.io / registry.fp.o , this may fix that, yeah. it should result in every IoT container image build getting synced to the registry, and the f42 ones should get the 'latest' tag.
Author
Contributor

so, no, I don't think so. Per https://pagure.io/fedora-iot/pungi-iot/blob/main/f/fedora-iot.conf , IoT does still compose and publish old-school ostrees, and that's what the user in 12508 is using, I think. so this doesn't affect that. I think the situation in 12508 is simply that there actually was no F42 IoT compose between 20250414 and 20250422.

so, no, I don't think so. Per https://pagure.io/fedora-iot/pungi-iot/blob/main/f/fedora-iot.conf , IoT does still compose and publish old-school ostrees, and that's what the user in 12508 is using, I think. so this doesn't affect that. I think the situation in 12508 is simply that there actually was no F42 IoT compose between 20250414 and 20250422.
Contributor

Yeah, the nightly container still builds f41 for iot... but I am not sure if it's supposed to switch or just fo 42 or what. ;( Will wait for @pwhalen to look.

Yeah, the nightly container still builds f41 for iot... but I am not sure if it's supposed to switch or just fo 42 or what. ;( Will wait for @pwhalen to look.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/ansible#2580
No description provided.