BOOTC-OCI-ARTIFACTS(7)

💖 BOOTC-OCI-ARTIFACTS 💖

okay bestie, so this is bootc-oci-artifacts — it lives in section 7 of the Miscellaneous Information Manual — and it's here to answer one very specific question: how does the use of OCI artifacts intersect with this effort? 🦋

---

✨ NAME ✨

bootc-oci-artifacts — how does the use of OCI artifacts intersect with this effort? 🎀

---

🌸 DESCRIPTION 🌸

Okay so first thing's first, no cap: the "bootc compatible" images are OCI container images, periodt. They do not rely on the OCI artifact specification or the OCI referrers API. Not a vibe they're going for, fr fr.

• OCI artifact specification: https://github.com/opencontainers/image-spec/blob/main/artifacts-guidance.md
• OCI referrers API: https://github.com/opencontainers/distribution-spec/blob/main/spec.md#enabling-the-referrers-api

---

Now, here's the tea ☕ — it's foreseeable that users are gonna need to produce "traditional" disk images from those "bootc compatible" container images, using additional tools. And when we say "traditional" disk images we mean like:

• raw disk images
• qcow2 disk images
• Amazon AMIs
• etc.

So therefore (iykyk), it's reasonable that some users may want to encapsulate those disk images as an OCI artifact for storage and distribution. Totally understandable, honestly, iconic behaviour 💅

🛑 BUT. Listen up. It is not a goal to use bootc to produce these "traditional" disk images, nor is it a goal to facilitate the encapsulation of those disk images as OCI artifacts. That's just not what bootc is doing here, and that's the whole point. 🚫✨

---

🫶 SEE ALSO 🫶

• bootc(8)
• bootc-docs(7)

---

👑 VERSION 👑

v1.17.1 ⭐

---

and that's the whole page bestie, no notes 💖 this was BOOTC-OCI-ARTIFACTS(7) from the Miscellaneous Information Manual, version v1.17.1 — slay, go forth and read bootc(8) and bootc-docs(7) 🌈🦋🎀