vmexec-exec(1)

💅 NAME

okay so bestie, let me introduce you to vmexec-exec — it runs a command in an existing virtual machine 🖥️✨. That's it, that's the whole vibe. You've already got a VM up and running, and you wanna poke something inside it. This is the girl for the job.

🌸 SYNOPSIS

vmexec exec [-e|--env] [-w|--workdir] [-s|--ssh-timeout]
[-i|--interactive] [-t|--tty] [-h|--help] <VMID> [ARGS]

like, that's the whole spell you're casting 💅 — a pile of flags, your <VMID>, and then whatever [ARGS] you want to actually run in there.

🦋 DESCRIPTION

Run a command in an existing virtual machine. That's THE description, no notes, she said what she said 💖 (the manual page itself is literally called vmexec-exec, section 1 of the General Commands Manual — so you know it's legit).

✨ OPTIONS ✨

• -e, --env <ENV> — set environment variables for the process inside the virtual machine 🌈 You can pass this bad boy multiple times — stack 'em up, one variable per flag. Expected format: KEY=VALUE (do not get cute with it, that's the format, periodt).
• -w, --workdir <WORKDIR> — the working directory inside the virtual machine 🎀 ngl the default working directory for running binaries inside a VM depends on the image. Most commonly, it'll be /root. So like, don't @ her if it's somewhere else, it's giving image-dependent energy 🙈
• -s, --ssh-timeout <SSH_TIMEOUT> — SSH connection timeout 🌸 [default: 20] She'll try for this long (in seconds) to connect to the virtual machine's SSH server. That's the whole assignment. Tick tock ⏳
• -i, --interactive <INTERACTIVE> — make STDIN available to the virtual machine's process 💖 [default: auto] If 'auto', this will try to read from stdin if it is available, and do nothing when stdin is not available. If 'always', this will try to read from stdin and abort when stdin is not available. No stdin, no service 😭 Possible values:
  • always — forward stdin and fail if it can't be opened (all or nothing, main character energy 👑)
  • never — don't forward stdin
  • auto — forward stdin if it can be opened, otherwise carry on without it (the chill one 🧚)
• -t, --tty <TTY> — allocate a pseudo-TTY for the virtual machine 🦋 [default: auto] If 'auto', this will be enabled in case vmexec is run from an interactive terminal. Yes she's checking the vibe first. Possible values:
  • always — allocate a pseudo-TTY
  • never — don't allocate a pseudo-TTY
  • auto — allocate a pseudo-TTY if stdout is a terminal
• -h, --help — print help (see a summary with '-h') 🫶 so helpful of her honestly
• <VMID> — identifier of a running virtual machine ⭐ note the running part bestie, she's not out here starting VMs for you 💀
• [ARGS] — arguments to run in the virtual machine 🔥 this is the whole point, this is the moment, this is the actual command

heads up babes: <VMID> has to be a running virtual machine, and -h gives you the full help while '-h' gives you the summary. Also -e stacks, so bring as many env vars as your heart desires 💜

🎀 see you, bestie

and that's the page!! footer's giving <pink>exec</pink> on the left and <pink>vmexec-exec(1)</pink> on the right of the General Commands Manual page — no version number, no date, just vibes and a section number. slay, honestly 💅✨🦋