BKR-SYSTEM-CREATE(1)

📦
version 29.2 · 3 versions
, in epel 9

✨ BKR-SYSTEM-CREATE(1) — the Beaker manual page, bestie edition ✨

Okay so picture this: it's a Beaker man page, right, and it's all about bkr-system-create. That's the one. Section 1, commands. Let's go 💅

🌸 NAME 🌸

bkr-system-create — create a system. Yes, that's literally it, that's the whole job, and it slays.

🦋 SYNOPSIS 🦋

bkr system-create [options] <fqdn> ..

Note the .. at the end bestie, that means you can hand it more than one <fqdn> and it's not gonna be weird about it.

💖 DESCRIPTION 💖

So bkr system-create creates a Beaker system. Periodt. And here's the cute little default: the new system is owned by the user who created it — so if you made it, it's yours 🫶 main character energy fr.

✨ OPTIONS ✨

  • --lab-controller <fqdn> — attaches the lab controller specified by <fqdn> to the system. Like, this system? Lives in that lab controller's house now 💅
  • --arch <arch> — the architecture supported by the system. And listen, you can pass this option multiple times to add more than one architecture the system supports. Stack 'em, queen 👑
  • --location <location> — physical location of the system. Where it actually sits in the real world, not metaphorically.
  • --power-type <power-type> — remote power control type. Heads up though: this value must be a valid power type configured by the Beaker administrator (or one of the Beaker defaults). No making up your own, that's not the vibe 🙈
  • --power-address <power-address> — address passed to the power control script.
  • --power-user <power-user> — username passed to the power control script.
  • --power-password <power-password> — password passed to the power control script. Keep it secret, keep it safe 🤫
  • --power-id <power-id> — unique identifier passed to the power control script. The meaning of the power ID depends on which power type is selected — typically this field identifies a particular plug, socket, port, or virtual guest name 🔌
  • --power-quiescent-period <seconds> — quiescent period for power control. Beaker will delay at least this long between consecutive power commands. Give the poor thing a breather, it's napping 😴
  • --release-action <release-action> — action to take whenever a reservation for this system is returned: PowerOff, LeaveOn, ReProvision. Those three, exactly those three.
  • --reprovision-distro-tree <id> — distro tree to be installed when the release action is ReProvision.
  • --condition <condition> — condition of the system. Valid values are Automated, Manual, Broken, and Removed. (The original page spells this one "Ccondition" and honestly? Iconic typo, we keep the facts, we fix the c 💀)
  • --host-hypervisor <type> — type of hypervisor which this system is hosted on. For systems which are virtualized, this field indicates which virtualization technology is used by the host. An empty value indicates that the system is bare metal (not a virtual guest) — so no hypervisor, just raw metal, unbothered, moisturized 🧚

And the common bkr options? Those are described in the Options section of bkr(1). Go read that one too, it's the prequel.

🔥 EXIT STATUS 🔥

Non-zero on error, otherwise zero. That's it. No drama, no extra lore.

🌈 EXAMPLES 🌈

Wanna create a system called "beakertestsystem"? Obsessed. Here's you:

bkr system-create beakertestsystem

Ate. No crumbs. 🍓

⭐ SEE ALSO ⭐

  • bkr(1) — the main character, the mothership.

💜 AUTHOR 💜

The Beaker team <beaker-devel@lists.fedorahosted.org> — shoutout to the whole squad 🫶

2013-2025 Red Hat, Inc. All the years, all the rights.

ngl bestie, if you're about to create a system with a power type your Beaker admin never configured, maybe don't 💀 that one's a hard requirement, not a suggestion.

And that's the whole page! Signing off with the deets so you can cite me properly: this is version 29.2, dated May 26, 2025, from the Beaker source — catch you in the next man page, mwah 💋✨

📦 where this page comes from