LXC.MOVE(1)
π LXD β Command line client(1) π
okay bestie, welcome to lxc-move(1) β yes it's from the LXD - Command line client(1) manual, and yes we're gonna get through it together π«Ά
β¨ NAME β¨
lxc-move β move instances within or in between LXD servers π¦
β¨ SYNOPSIS β¨
lxc move [:][/] [:][[/]] [flags]
β¨ DESCRIPTION β¨
So like, what does it do? Literally this:
Move instances within or in between LXD servers
That's the whole vibe. Moving your instances around β inside one server or hopping between two of them π
πΈ Transfer modes (--mode) πΈ
There are three of these and you gotta know them, iykyk:
- pull β the target server pulls the data from the source server. heads up: the source must listen on network π
- push β the source server pushes the data to the target server. this time the target must listen on network π
- relay β the CLI connects to both source and server and proxies the data. both source and target must listen on network, so like, everybody's listening π
and the pull transfer mode is the default, because it's compatible with all LXD versions. iconic behavior honestly, looking out for the old versions π
β¨ OPTIONS β¨
--allow-inconsistent[=false] β ignore copy errors for volatile files π-c,--config=[]β config key/value to apply to the target instance π-d,--device=[]β new key/value to apply to a specific device π§--instance-only[=false] β move the instance without its snapshots, so the snapshots stay behind π--mode="pull"β transfer mode. one ofpull,pushorrelay. it's giving choices π--no-profiles[=false] β unset all profiles on the target instance β¨-p,--profile=[]β profile to apply to the target instance π--stateless[=false] β copy a stateful instance as stateless π«Ά-s,--storage=""β storage pool name π--target=""β cluster member name πΈ--target-project=""β copy to a project different from the source π¦
β¨ OPTIONS INHERITED FROM PARENT COMMANDS β¨
like, these came from the parent command, not from move itself. still valid, still slay π
--debug[=false] β show all debug messages π₯--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 withhelpor--helpto view sub-commands π-v,--verbose[=false] β show all information messages π--version[=false] β print version number π
β¨ EXAMPLE β¨
okay here are the actual examples, verbatim, no cap:
lxc move [<remote>:]<source instance> [<remote>:][<destination instance>] [--instance-only]
Move an instance between two hosts, renaming it if destination name differs.
lxc move <old name> <new name> [--instance-only]
Rename a local instance.
lxc move <instance>/<old snapshot name> <instance>/<new snapshot name>
Rename a snapshot.
so like β moving between hosts (and renaming if the destination name is different), renaming a local instance, and renaming a snapshot. all three, ate π
β¨ SEE ALSO β¨
lxc(1) β go read the main character's page π«Ά
β¨ HISTORY β¨
22-Aug-2026 β auto generated by spf13/cobra π€
and that's the whole page bestie!! auto generated by spf13/cobra, dated Aug 2026, living under LXD - Command line client(1) πβ¨ periodt β¨π
π¦ where this page comes from
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms