Dusty Mabe
Dusty Mabe
@udf2457 I'm not sure if we should really document this case, but maybe? Either way the process (right now) would look very similar to https://docs.fedoraproject.org/en-US/fedora-coreos/os-extensions/ except you just `rpm-ostree rebase`...
what's the image you propose replacing it with?
Let's do it!
I want to review this thoroughly and I'm out of time right now. One note off hand is that maybe we should consider modifying the instructions at the top under...
> However, the difference would be that after the initial installation, the system would have a persistent read-write overlay on top of the root. With this persistent read-write overlay I'm...
> I think you're right. The most likely scenario is that when I opened #1130 way back when, I was focused on the x86_64 case and didn't realize that in...
> Also thanks to usage of `osmet` images fetching separate `dasd.s390x.raw` became obsolete. Maybe it makes sense to completely drop it? Are you saying that absolutely nothing uses it today?
The OpenShift documentation hasn't mentioned dasd since 4.5: https://docs.openshift.com/container-platform/4.5/installing/installing_ibm_z/installing-ibm-z.html
we removed dasd from our build artifacts in RHCOS. At some point in the future we should be able to remove the code that supports building them (or probably more...
Installing to a non-empty disk should be a non-issue (`coreos-installer` will just happily overwrite what is there), but I'd be worried about false positives where the install from the previous...