SCOS does not allow updating

[kai-uwe-rommel]

I know that for RHCOS this is probably intentional.
But SCOS is (IMO) more generic and could allow updating (like FCOS does)?

[root@scos ~]# rpm-ostree upgrade --check
error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: creating temp directory: archive file not found: "/scos-9.0.20250510-0-ostree.x86_64.ociarchive"

Actually, RHCOS does at least not fail this way:

[root@worker-01 ~]# rpm-ostree upgrade --check
No updates available.

E.g. RHCOS gracefully reports that there is no update while SCOS fails completely at this point.

[Prashanth684]

/cc @jlebon

[jlebon]

Right, yeah. Currently, the primary use case for SCOS is as part of OKD where it's managed by the MCO like RHCOS. In Image Mode spirit though, you can absolutely build custom bootable container images on top of the SCOS base image or directly on top of centos-bootc and use the SCOS disk images simply to bootstrap if that's more convenient (e.g. Ignition/Afterburn).

I agree though we should at the very least make rpm-ostree upgrade error out more nicely.