LXC.MOVE(1)

πŸ“¦
version 5.21.6 Β· 3 versions
, in opensuse-leap 16.0

πŸ’… 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 of pull, push or relay. 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 with help or --help to 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