OSTREE.REPO(5)

💖 NAME 💖

ostree.repo — OSTree repository configuration and layout. Also hi bestie, this page is literally ostree.repo(5), and we're about to vibe-check the whole repo setup. ✨

🦋 DESCRIPTION 🦋

okay so an OSTree repository is structurally similar to a git repository. It's a content-addressed object store containing filesystem trees. But — and this is the main character twist — unlike git, ostree is designed to store operating system binaries. It records the Unix uid and gid, permissions, as well as extended attributes. Not me being obsessed with metadata, but here we are 💅.

A repository can be in one of three modes:

• bare — designed as a hard link source for operating system checkouts.
• bare-user — like bare, but it works on systems that run as non-root as well as non-root containers.
• archive-z2 — designed for static HTTP servers.

There is a system repository located at /ostree/repo. If no repository is specified — either by a command-line option or the OSTREE_REPO environment variable — ostree as well as many API calls will use it by default. So yes, that's the default default, bestie. 🫶

🎀 COMPONENTS OF A REPOSITORY 🎀

The only user-editable component is the config file. For more information, see ostree.repo-config(5). That's the whole component situation — one editable file, iconic minimalism. 💖

🌈 SEE ALSO 🌈

• ostree(1)
• ostree.repo-config(1)

tiny note from your girl: COMPONENTS says ostree.repo-config(5) and SEE ALSO says ostree.repo-config(1) — I'm keeping both exactly as written, no editing, no cap. 💅

---

Source/version: OSTree. Manual: OSTREE.REPO(5). Date: not in this footer, bestie — so we're not inventing one. That's the page! Go be iconic with your content-addressed object store. 🎀✨