When performing ostree local updates, users need to upload the .tar file generated with the Edge Commit to a server and then unpack them into an specific directory. The request is for including this functionality in the UI so the upload and unpackaging processes can be handled by cockpit. Something like: adding a "upload commit" option in the UI, and when there's a new commit staged a "reboot into it" option.
> the .tar file generated with the Edge Commit Hmm, that feels like a sad user experience. You have to download a huge tarball from the system that builds the edge image to some laptop/workstation, and upload it again to the destination machine? What other output options does your image build process offer? Is that the image builder on cloud.redhat.com (Sorry, I'm not very familiar with it), or a self-hosted instance?. In my experience, OSTree builds result in either some http-accessible OSTree repository (classic), or pushing it as OCI container image into some registry [1], which is relatively new, but super convenient. We are working on cockpit-ostree support for the latter [2]. CC'ing Tom as the image builder lead for your interest, maybe you also have some ideas about how this should look like. [1] https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable [2] https://issues.redhat.com/browse/COCKPIT-928