Suggested archive mechanism - from registry using ORAS

[vsoch]

Hiya! Instead of requiring an https address for a .tar.gz, I want to suggest looking at ORAS: https://oras.land/

Of course it would depend on the language you implemented wave in (Go I hope?) but with oras you could allow a user to specify a specific docker URI and blob digest, and get the manifest and request the blob directly without needing to extract it, put it somewhere special, and do that every time there is an update.

I just realized the hard way building my "single layer with flux" that is the chonkiest chonker you've ever seen - I'm not going to have a place to put it to download (releases on GitHub are limited to 25MB). My layer is too chonky, and even if I split it up into smaller pieces, it would take ~34 to get it working (which is unlikely) so I need to figure out some other way!

[pditommaso]

We are looking into this right now. Indeed, the idea is to allow container augmentation (ie. layers injection) via another container image. The user should take care to create it using FORM scratch to not include undeeded content.

How ORAS improves over this?

[vsoch]

Oras would allow you to select a specific layer in any image (not necessarily having to be from scratch) and extract it. It works by way of allowing you to read the manifest and then retrieve (or otherwise interact with) specific blobs.

[pditommaso]

Interesting. I'll give a better look