BOOTC-EX...GRESS-FD(7)
π NAME π
bootc-experimental-progress-fd β interactive progress with --progress-fd, bestie π«Ά
β¨ DESCRIPTION β¨
Okay so first thing, no cap: this is an experimental feature. Like, we're in our beta era. The tracking issue lives here if you wanna watch the drama unfold: β¨https://github.com/bootc-dev/bootc/issues/1016β© π
So boom β the bootc status tooling already lets a client discover the state of the system, right? Adorable. But when you're doing interactive changes, like bootc upgrade or bootc switch, you can actually monitor the status of downloads and other operations at a fine-grained level with --progress-fd. She's nosy and we love that for her π
The format of data output over --progress-fd is JSON Lines β¨https://jsonlines.orgβ©, which is literally just a series of JSON objects separated by newlines. And important detail: the intermediate JSON content is guaranteed not to contain a literal newline. So you can parse it without crying π
Wanna see the JSON schema describing this version? It's right here: progress-v0.schema.json β¨https://bootc.dev/bootc/progress-v0.schema.jsonβ©. Slay.
Deploying a new image with either switch or upgrade is a three-stage production, and yes, it's giving main character energy:
- pulling β this step downloads the image from the registry, offering per-layer and progress in each message π
- importing β this step imports the image into storage and consists of a single step
- staging β this runs a variety of staging tasks. Currently, they are staging the image to disk, pulling bound images, and removing old images π
Not me reminding you: new stages or fields may be added at any time. The format is a moving target, so don't hardcode your whole personality around it π
A lil vibe check on timing, because the way these stages behave is so dependent on stuff:
- Importing and staging are affected by disk speed and the total image size.
- Pulling is affected by network speed and how many layers invalidate between pulls.
Therefore, a large image with a good caching strategy will have longer importing and staging times, and a small bespoke container image will have negligible importing and staging times. That's just the physics of it, fr fr π¦
πΈ SEE ALSO πΈ
π VERSION π
v1.17.1
And that's the whole page, bestie! This one's from the Miscellaneous Information Manual β BOOTC-EX...GRESS-FD(7) β rocking version v1.17.1, and yeah the header and footer both just say BOOTC-EX...GRESS-FD(7) because the manpage is obsessed with itself π Go monitor some downloads, you icon. Periodt. π
π¦ where this page comes from
- fedora 43: bootc 1.17.1-1.fc43 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- fedora 44: bootc 1.17.1-1.fc44 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms