-
Notifications
You must be signed in to change notification settings - Fork 63
Closed
Labels
area/bootable-containersRelated to the bootable containers effort.Related to the bootable containers effort.jirafor syncing to jirafor syncing to jirakind/enhancementstatus/decidedstatus/pending-actionNeeds actionNeeds action
Description
Can we get container tags for each FCOS release so we can pin to a specific version or roll back to a specific version if we encounter issues with one of the stream layer updates?
For example coreos/butane#428 has me blocked with the current quay.io/fedora/fedora-coreos:stable
tag being unusable. I can't pull an older image by SHA because quay.io seems to prune untagged SHAs over time which is making it hard for me to roll back until coreos/butane#428 gets addressed. I wish I could just pull quay.io/fedora/fedora-coreos:36.20221001.3.0
for example.
It would be super great to have a history of each FCOS release as a container tag so we can have a safety net for rollbacks.
joshdrake and anthr76
Metadata
Metadata
Assignees
Labels
area/bootable-containersRelated to the bootable containers effort.Related to the bootable containers effort.jirafor syncing to jirafor syncing to jirakind/enhancementstatus/decidedstatus/pending-actionNeeds actionNeeds action