LXD.INIT(1)
π lxd init β the manual, but make it make sense π
okay bestie, welcome to lxd.init(1) β yes it's from the LXD - Container server manual, and yes it's literally the glow-up ritual for your LXD daemon. Sit down, hydrate, let's configure a container server together π§β¨
πΈ NAME πΈ
lxd-init β Configure the LXD daemon
like. that's the whole job. you're setting up the daemon. iconic behavior honestly π
β¨ SYNOPSIS β¨
lxd init [flags]
that's it. that's the whole summoning spell. flags go brrr π¦
π DESCRIPTION π
Description: Configure the LXD daemon.
lowkey the most self-explanatory description ever written but we respect it. this is the command you run to set up your LXD daemon β could be interactive (default vibe, it asks you stuff), could be fully automatic (no thoughts head empty mode), could be preseeded from a YAML config, or could just dump the YAML at you. pick your fighter π
π OPTIONS π
--auto[=false]β Automatic (non-interactive) mode. it just goes. no questions, no small talk, main character energy β¨--dump[=false]β Dump YAML config to stdout. it shows you the config in YAML instead of doing anything with it π«Ά--minimal[=false]β Minimal configuration (non-interactive). the bare minimum, the "I woke up and chose simplicity" setting πΈ--network-address=""β Address to bind LXD to (default: none)``--network-port=-1β Port to bind LXD to (default: 8443)``--preseed[=false]β Pre-seed mode, expects YAML config from stdin. feed it YAML through stdin and it eats π--storage-backend=""β Storage backend to use (btrfs, dir, lvm or zfs, default: dir)``--storage-create-device=""β Setup device based storage using DEVICE``--storage-create-loop=-1β Setup loop based storage with SIZE in GiB``--storage-pool=""β Storage pool to use or create``--trust-password=""β Password required to add new clients``
ngl the storage ones are the ones people always get confused about, so read them twice bestie, no cap π₯
π OPTIONS INHERITED FROM PARENT COMMANDS π
these are the ones the parent command was like "here, take these too" β they're not lxd init's own but they show up anyway π
-d,--debug[=false]β Show all debug messages. the receipts. every single one π-h,--help[=false]β Print help--logfile=""β Path to the log file``--syslog[=false]β Log to syslog--trace=[]β Log tracing targets``-v,--verbose[=false]β Show all information messages. it's giving chatty β¨--version[=false]β Print version number
π¦ EXAMPLE π¦
the canonical examples, verbatim, do not touch, they're perfect:
init --minimal
init --auto [--network-address=IP] [--network-port=8443] [--storage-backend=dir]
[--storage-create-device=DEVICE] [--storage-create-loop=SIZE]
[--storage-pool=POOL] [--trust-password=PASSWORD]
init --preseed
init --dump
so you got: the minimal girlie route, the full auto route with all the bracket options stacked like a lil outfit, the preseed route (stdin YAML, very demure), and the dump route (just show me the YAML, I'm nosy) π
π SEE ALSO π
go read that one too, it's the parent, it's giving family reunion πΈ
β HISTORY β
27-Jun-2026β Auto generated byspf13/cobra
fr fr: this whole page was Auto generated by spf13/cobra β that's the source/version vibe and the Jun 2026 date stamp, and the manual itself is the LXD - Container server(1) one. so like. shoutout to cobra for writing my homework for me πβ¨
that's the whole page bestie, go configure ur daemon, u got this ππ«Άπ
π¦ where this page comes from
- debian trixie: lxd 5.0.2+git20231211.1364ae4-9+deb13u7 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms