max / alloy

Measure the adopt verb over containers-storage, not just registry The switch section recorded c1 -> c2 over --transport registry. The update channel has the machine build its own image, so the ref is in that machine's local store and the verb is --transport containers-storage. That transport had never been exercised, and a design resting on "same verb, should carry" is resting on an argument. It carries. switch succeeds where upgrade refuses, the layer is discarded with Diff: 1 removed visible before the reboot, the rollback keeps it, and the re-layer resolves out of the new image's carried repo with the network repo disabled. Two things the run adds. The adopt is nearly free -- 69 layers already present against 4 needed totalling 6.1 kB -- so tier 2 pays for the build and not the switch. And rpm-ostree install over a non-tty ssh completes its transaction and never exits, which reads exactly like a slow depsolve; that one cost this run fifteen minutes and is written down so it costs the next one nothing.