On 10/24/22 23:45, Dusty Mabe wrote:
On 10/13/22 15:08, Ben Cotton wrote:
>
> An update will be shipped that will cause existing systems tracking
> the production ostree branches to be switched to the corresponding
> container image. Concretely for example, a system running
> `fedora:fedora/36/x86_64/silverblue` will execute `rpm-ostree rebase
> ostree-remote-registry:fedora:quay.io/fedora/fedora-silverblue:36`.
I don't think I'm comfortable with making this switch by default for some
time (certainly not in the F38 time frame). We currently only have the
container image in place for one edition (Fedora CoreOS) and FCOS isn't
even ready (you mention the design issue below).
This will probably take a few cycles. What we need to do now is come up
with a plan and then implement it over time.
And to be clear. What will take a few cycles is fully adopting this
proposal. There are certainly pieces of it that work already today.