-
Notifications
You must be signed in to change notification settings - Fork 168
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Support
ostree-format: oci
in image.yaml
Part of implementing coreos/fedora-coreos-tracker#812 A whole lot of the story of coreos-assembler is threaded with the tension between ostree and disk images. They have fundamentally different tradeoffs. And now I'm trying to add container images to the mix. The idea of capturing an ostree repo in archive mode as a tarball is a cosa invention. We don't actually ship anything that way. The proposal in the above linked issue is to "productize" support for shipping ostree-in-container, because containers are just slightly fancy tarballs. This patch adds support for: `echo 'ostree-format: oci' >> image.yaml` in the config git. When enabled, the `images/ostree` is replaced with an `oci-archive` format of an "ostree-in-container", which we might shorten to `ostcontainer` or so. The code is updated to call out to rpm-ostree's latest (really ostree-rs-ext's latest) code to perform the export and import. We're not making it the default yet, but I'd like to potentially e.g. switch the FCOS `next` stream or so. The next step after this lands is to add separate code in the pipeline to push the image to a registry. There's also a *lot* of deduplication/rationalization to come later around `cosa upload-oscontainer` etc.
- Loading branch information
Showing
3 changed files
with
50 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters