LXD to Incus host-to-host migration caveats and working practices

Incus
2

You may add to this the following

  1. when you migrate with lxd-to-incus, the existing private bridge (by default, lxdbr0) remains in the migrated setup. This makes sense as a way to cover instances that specifically have lxdbr0 in their configuration. When cleaning up, you may try renaming the interface to incusbr0 as a way to wean out any network configuration that uses the hard-coded interface name.
  2. when you migrate with lxd-to-incus, the dnsmasq process that takes care of the managed network now configures the instance names to have suffix .incus (instead of the old .lxd). That is, before: mycontainer.lxd, now mycontainer.incus. This could cause trouble if your instances are configured to use those hostnames with suffices. There’s a workaround to keep the old suffix until you fix the configuration files.