You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello all, I'm involved with the Universal Blue project and specifically the uCore home server image which has been based on FCOS. The Universal Blue project started when ostree native containers become a reality for building customized versions of Fedora, and uCore followed suit. But since the beginning, there have been talks of "wouldn't it be great if we had a CentOS based uCore" since most users like the idea of long running, stable servers rather than the faster update cycle of Fedora.
One thing which as come up, especially as someone not coming from an OKD and OpenShift background, it's not immediately obvious which tag of the image to use.
These are some of the image tags I've looked at:
quay.io/okd/centos-stream-coreos-9:4.17-x86_64
quay.io/okd/centos-stream-coreos-9:4.18-x86_64
quay.io/okd/centos-stream-coreos-10:4.18-x86_64
By looking at other information (including the blog post above), I believe 4.17 is more or less stable and 4.18 is testing to borrow the terms from FCOS.
My request is that a stable tag be added to SCOS so the images can be more easily used for generic purposes.
I'm personally indifferent if it's stable or stable-x86_64, etc, but I image if 4.17 is stable today, when 4.18 is officially released, the stable tag could follow the version change.
Does this seem reasonable to the team here?
The text was updated successfully, but these errors were encountered:
My request is that a stable tag be added to SCOS so the images can be more easily used for generic purposes.
These images are not meant to be used for generic purposes. They are specifically created for OKD to be layered on top of the pure centos bootimage on the OKD nodes. We are working on making the base boot images public and will link to those once we have them.
Hello all, I'm involved with the Universal Blue project and specifically the uCore home server image which has been based on FCOS. The Universal Blue project started when ostree native containers become a reality for building customized versions of Fedora, and uCore followed suit. But since the beginning, there have been talks of "wouldn't it be great if we had a CentOS based uCore" since most users like the idea of long running, stable servers rather than the faster update cycle of Fedora.
Now that OKD is based on SCOS ( https://okd.io/blog/2024/12/16/okd-4-16-and-4-17-release#node-operating-systems-are-now-based-off-centos-stream-coreos-scos ) and there are regularly published SCOS images ( https://quay.io/repository/okd/centos-stream-coreos-9?tab=tags ), I've started tinkering with building uCore on SCOS instead of FCOS.
One thing which as come up, especially as someone not coming from an OKD and OpenShift background, it's not immediately obvious which tag of the image to use.
These are some of the image tags I've looked at:
By looking at other information (including the blog post above), I believe
4.17
is more or lessstable
and4.18
istesting
to borrow the terms from FCOS.My request is that a
stable
tag be added to SCOS so the images can be more easily used for generic purposes.I'm personally indifferent if it's
stable
orstable-x86_64
, etc, but I image if4.17
isstable
today, when4.18
is officially released, thestable
tag could follow the version change.Does this seem reasonable to the team here?
The text was updated successfully, but these errors were encountered: