INCUS.LAUNCH(1)

πŸ’– INCUS-LAUNCH πŸ’–

okay bestie, welcome to Incus - Command line client (that's the manual name, page 1, she's iconic). this lil page is all about incus-launch, and it's genuinely one of the most fun commands in the whole toolbox. let's get into it 🫢


✨ NAME ✨

incus-launch β€” create and start instances from images. that's it, that's the vibe. you point at an image, she makes you an instance, done. πŸ’…


🌸 SYNOPSIS 🌸

incus launch (--empty|[:]) [:][] [flags]

periodt. that's the shape of it: you can go --empty, or give it a remote image thing like [:], then the instance name [:], then whatever [flags] your heart desires. πŸ¦‹


πŸŽ€ DESCRIPTION πŸŽ€

Description:

  • create and start instances from images 🌈

like... she creates it AND starts it. no extra steps, no "oh now you have to run incus start", none of that. main character behaviour fr fr. ✨


πŸ’œ OPTIONS πŸ’œ

  • -c, --config=[] β€” config key/value to slap onto your brand new instance πŸ“
  • --console[=""] β€” immediately attach to the console, no chill, straight in
  • --description="" β€” give your instance a lil description (she deserves one)
  • -d, --device=[] β€” a new key/value to apply to a specific device πŸ”§
  • --empty[=false] β€” create an empty instance (no image, just vibes)
  • --environment-file="" β€” pull environment variables in from a file 🌱
  • -e, --ephemeral[=false] β€” ephemeral instance (here for a good time, not a long time)
  • -n, --network="" β€” network name πŸ•ΈοΈ
  • --no-profiles[=false] β€” create the instance with no profiles applied (bare, unbothered, moisturized)
  • -p, --profile=[] β€” profile to apply to the new instance
  • -s, --storage="" β€” storage pool name πŸ’Ύ
  • --target="" β€” cluster member name (for the multi-machine girlies)
  • -t, --type="" β€” instance type
  • --vm[=false] β€” create a virtual machine instead of a container πŸ–₯️✨

OPTIONS INHERITED FROM PARENT COMMANDS

  • --debug[=false] β€” show all debug messages πŸ›
  • --explain[=false] β€” if the command is valid, explain its parsed arguments instead of running it (she's a professor, not a runner)
  • --force-local[=false] β€” force using the local unix socket
  • -h, --help[=false] β€” print help 🫢
  • --project="" β€” override the source project
  • -q, --quiet[=false] β€” don't show progress information 🀫
  • --sub-commands[=false] β€” use with help or --help to view sub-commands
  • -v, --verbose[=false] β€” show all information messages πŸ“’
  • --version[=false] β€” print version number

🌟 EXAMPLE 🌟

these are literally the receipts. copy them exactly bestie, no cap. πŸ’–
  incus launch images:debian/12 c1
      Create and start a container named "c1"

  incus launch images:debian/12 c2 < config.yaml
      Create and start a container named "c2" with configuration from config.yaml

  incus launch images:debian/12 c3 -t aws:t2.micro
      Create and start a container named "c3" using the same size as an AWS t2.micro (1 vCPU, 1GiB of RAM)

  incus launch images:debian/12 v1 --vm -c limits.cpu=4 -c limits.memory=4GiB
      Create and start a virtual machine named "v1" with 4 vCPUs and 4GiB of RAM

  incus launch images:debian/12 v2 --vm -d root,size=50GiB -d root,io.bus=nvme
      Create and start a virtual machine named "v2", overriding the disk size and bus

the < config.yaml one?? she's reading stdin like it's a group chat. obsessed. 😭


πŸ¦‹ SEE ALSO πŸ¦‹

  • incus(1) β€” go say hi to the parent, she raised this one πŸ’œ

πŸ“œ HISTORY πŸ“œ

24-Sep-2026 Auto generated by spf13/cobra


and that's the whole page bestie!! this one was auto generated by spf13/cobra, dated Sep 2026, and it belongs to Incus - Command line client(1). go forth and launch something gorgeous. slay, ate, no crumbs. πŸ‘‘πŸ’…πŸŒˆ

πŸ“¦ where this page comes from