lxc-user-nic(1)

🌸 NAME 🌸

lxc-user-nic — manage nics in another network namespace. That's the whole vibe, bestie: this is the little helper that handles network interfaces for you 💖

---

✨ SYNOPSIS ✨

Okay so it's got two modes, literally:

lxc-user-nic create {lxcpath} {name} {pid} {type} {bridge} {container
             nicname}
lxc-user-nic delete {lxcpath} {name} {path to network namespace} {type}
             {bridge} {container nicname}

---

💅 DESCRIPTION 💅

So lxc-user-nic is a setuid-root program — yes, that's the big-deal part — with which unprivileged users may manage network interfaces for use by a lxc container. It's giving "trusted little helper with main character energy" 🔥

It will consult the configuration file /etc/lxc/lxc-usernet to determine the number of interfaces which the calling user is allowed to create, and which bridge they may attach them to. Yep, that file is the vibe check for your limits 👑

It tracks the number of interfaces each user has created using the file /run/lxc/nics. Lowkey important.

It ensures that the calling user is privileged over the network namespace to which the interface will be attached. No sneaking into random netns, not on its watch 🙈

lxc-user-nic also allows one to delete network devices. Currently only ovs ports can be deleted — that's the limit, fr fr.

---

🎀 OPTIONS 🎀

• lxcpath — the path of the container. This is currently not used. It's just sitting there being iconic and unused 💅
• name — the name of the container. This is currently not used either. Also just vibing.
• pid — the process id for the task to whose network namespace the interface should be attached. That's the target netns energy 🎯
• type — the network interface type to attach. Currently only veth is supported. With this type, two interfaces representing each tunnel endpoint are created. One endpoint will be attached to the specified bridge, while the other will be passed into the container. Twin interfaces, one tunnel, slay 🦋
• bridge — the bridge to which to attach the network interface, for instance lxcbr0. That's the bridge bestie 🫶
• container nicname — the desired interface name in the container. This will be eth0 if unspecified. Default queen behavior 👑
• path to network namespace — a path to open to get a file descriptor for the target network namespace. This is only relevant when an veth device is deleted. Very "only when you need it" of it 💜

---

🦋 SEE ALSO 🦋

lxc(1), lxc-start(1), lxc-usernet(5) — go read those too, iykyk 🌈

---

Byeee 💋 — this page is dated 2026-05-01 and belongs to the lxc-user-nic(1) manual page; go be iconic with your netns 🫶