INCUS.CONFIG.SET(1)

πŸ’– incus-config-set β€” set instance or server config keys πŸ’–

okay so real talk bestie, you've landed in the Incus command line client manual, section 1, and this little page is all about incus config set. yes. that one. the glow-up button for your config keys ✨


✨ NAME ✨

incus-config-set β€” set instance or server config keys πŸŽ€


🌸 SYNOPSIS 🌸

incus config set [:][[/]] =... [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

so like. Set instance or server configuration keys. that's the whole vibe. that's the job πŸ’…

and listen, for backward compatibility, you can still set a single configuration key the old-school way, like this:

incus config set [:][]

(yes, the legacy form still works. iconic of it honestly. it refuses to be left behind πŸ™ˆ)


πŸ’… OPTIONS πŸ’…

  • -p, --property[=false] β€” set the key as an instance property instead of a regular config key πŸ‘‘
  • --target="" β€” the cluster member name you wanna aim this at 🌈

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these bad boys come down from the parent command, so they ride along with everything you do here:

  • --debug[=false] β€” show all the debug messages. every last one. she's chatty fr fr πŸ’€
  • --explain[=false] β€” if the command is valid, explain its parsed arguments instead of actually running it. lowkey a genius move πŸ”₯
  • --force-local[=false] β€” force using the local unix socket 🫢
  • -h, --help[=false] β€” print help. your bestie when you're lost 😭
  • --project="" β€” override the source project ✨
  • -q, --quiet[=false] β€” don't show progress information. silent mode, main character energy, no narration πŸŒ™
  • --sub-commands[=false] β€” use this with help or --help to view sub-commands πŸ‘€
  • -v, --verbose[=false] β€” show all information messages. she tells you everything πŸ“
  • --version[=false] β€” print version number. simple. iconic. πŸ’œ

⭐ EXAMPLE ⭐

okay these examples ate, let's go one by one:

  incus config set [<remote>:]<instance> limits.cpu=2

➑️ will set a CPU limit of "2" for the instance. yes, just like that. πŸ’ͺ


  incus config set my-instance cloud-init.user-data - < cloud-init.yaml

➑️ sets the cloud-init user-data for instance "my-instance" by reading "cloud-init.yaml" through stdin. piping queen 🌊


  incus config set core.https_address=[::]:8443

➑️ will have the server listen on IPv4 and IPv6 port 8443. both at once. she's flexible πŸ’–


πŸ”₯ SEE ALSO πŸ”₯

  • incus-config(1) β€” go read her, she's the whole family 🫢

🌈 HISTORY 🌈

  • 24-Sep-2026 β€” auto generated by spf13/cobra πŸ€–

pssst, one more thing before you go: this page was Auto generated by spf13/cobra, dated Sep 2026, and it lives in the Incus - Command line client(1) manual. slay, go set some keys bestie πŸ’…βœ¨πŸŽ€
πŸ“¦ where this page comes from