COMPOSER-CLI(1)

πŸ’– COMPOSER-CLI πŸ’– (that's the manual name bestie, section 1, we're in composer-cli territory)

✨ NAME ✨

composer-cli-compose-start-ostree β€” start an ostree compose using the blueprint and output type you picked, no cap


🌸 SYNOPSIS 🌸

composer-cli compose start-ostree BLUEPRINT TYPE [IMAGE-NAME PROFILE.TOML] [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so start an ostree compose using the blueprint and output type you selected. That's the whole vibe. πŸ’…

You can optionally start an upload too, if you're feeling ambitious.

--size is supported by osbuild-composer, and is in MiB. Just so we're clear on units, because units matter and guessing is not the move.

The full details of the start-ostree command can be viewed here, and honestly go look, it's giving documentation:

https://osbuild.org/docs/on-premises/commandline/building-ostree-images

πŸŽ€ OPTIONS πŸŽ€

  • -h, --help[=false] β€” help for start-ostree. Your little "what does this even do" button 🫢
  • --parent="" β€” OSTree parent
  • --poll="10s" β€” polling interval. How often we peek. πŸ‘€
  • --ref="" β€” OSTree reference
  • --size=0 β€” size of image in MiB
  • --timeout="5m" β€” maximum time to wait
  • --url="" β€” OSTree url
  • --wait[=false] β€” wait for compose to finish. Patience era. ⏳

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

These came with the family, we didn't pick them, but they're iconic anyway:

  • -a, --api=1 β€” WELDR Server API Version to use
  • --cloudsocket="/run/cloudapi/api.socket" β€” path to the cloudapi server's socket file
  • -j, --json[=false] β€” output the raw JSON response instead of the normal output
  • --log="" β€” path to optional logfile
  • -s, --socket="/run/weldr/api.socket" β€” path to the WELDR API server's socket file
  • --test=0 β€” pass test mode to compose. 1=Mock compose with fail. 2=Mock compose with finished.
  • --weldr-only[=false] β€” only use the WELDR API; skip using the newer Cloud API

🌈 EXAMPLE 🌈

Look at these. Main character commands fr fr:

composer-cli compose start-ostree tmux-image fedora-iot-container
composer-cli compose start-ostree tmux-image fedora-iot-container iot-name upload.toml
composer-cli compose start-ostree --ref "rhel/edge/example" tmux-image fedora-iot-container
composer-cli compose start-ostree --ref "rhel/edge/example" --url http://10.0.2.2:8080/repo/ empty fedora-iot-installer

⭐ SEE ALSO ⭐


🧚 HISTORY 🧚

28-Apr-2026 β€” Auto generated by spf13/cobra. Not me writing my own lore, the tool did it. πŸ€–


that's the whole page bestie, go start that ostree compose, you've got this πŸ’–βœ¨

Sign-off vibes: this is from the composer-cli manual, dated Apr 2026, section 1. Periodt. πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from