INCUS.NETWORK.PEER.CREATE(1)

📦
version 7.0.1 · 11 versions
, in ubuntu stonking

💖 incus-network-peer-create — it's giving "let's make networks be besties" 💖

okay so real quick before we dive in: this page lives in the Incus - Command line client manual (section 1, iykyk), and it's literally about creating a new network peering. That's it. That's the whole vibe. You're introducing two networks to each other. Networking but make it a meet-cute. 🦋

✨ NAME ✨

incus-network-peer-create — create new network peering, no cap 👑

🎀 SYNOPSIS 🎀

incus network peer create [:]  [/] [=...] [flags]

🌸 DESCRIPTION 🌸

Description:

Create new network peering 🫶

that's the whole thing bestie. you spawn a peering. the networks say hi. iconic behaviour.

💅 OPTIONS 💅

  • --description="" — the peer description 💬 (defaults to empty string, so nothing, which is valid, live your truth)
  • -t, --type="local" — type of peer, it's either local or remote 🌍 (defaults to local)

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

these come down from the parent command, like hand-me-downs but actually useful:

  • --debug[=false] — show all debug messages 🐛 (default false)
  • --explain[=false] — if the command is valid, explain its parsed arguments instead of running it 🤔 (default false) — yes this is the "read me the notes before you do the thing" flag, obsessed
  • --force-local[=false] — force using the local unix socket 🔌 (default false)
  • -h, --help[=false] — print help 🙋‍♀️ (default false)
  • --project="" — override the source project 🗂️ (default empty string)
  • -q, --quiet[=false] — don't show progress information 🤫 (default false)
  • --sub-commands[=false] — use with help or --help to view sub-commands 🌿 (default false)
  • -v, --verbose[=false] — show all information messages 📢 (default false)
  • --version[=false] — print version number 🏷️ (default false)

🌈 EXAMPLE 🌈

here's the part where we actually do stuff. three (3) whole examples, all of them fire:

  incus network peer create default peer1 web/default
      Create a new peering between network "default" in the current project and network "default" in the "web" project
  incus network peer create default peer2 ovn-ic --type=remote
      Create a new peering between network "default" in the current project and other remote networks through the "ovn-ic" integration
  incus network peer create default peer3 web/default < config.yaml
       Create a new peering between network default in the current project and network default in the web project using the configuration
       in the file config.yaml

like… the third one is piping a config file straight in?? main character energy fr fr 💀✨

🧚 SEE ALSO 🧚

  • incus-network-peer(1)

go read the parent one too, it's the prequel and it ate 💜

⭐ HISTORY ⭐

  • 24-Sep-2026 — Auto generated by spf13/cobra
lowkey important: this whole page was Auto generated by spf13/cobra, so don't come for me about the formatting, the humans didn't write it, the robot did 🤖

and that's the whole thing bestie!! 🎀✨ this page was Auto generated by spf13/cobra, version dated Sep 2026, living happily inside the Incus - Command line client manual (section 1) 💖 go forth and make those peers, you're doing amazing sweetie 🫶🌸

📦 where this page comes from