After an Incus migration, is there an equivalent to the "lxd init --dump" command?

When still using LXD, I used the command lxd init --dump to backup my server configuration to a file, which in one short, concise file showed the custom setup I had for (in my case) storage pools and profiles*.

The lxd command no longer exists, and running incus init --dump shows the message Error: unknown flag: --dump.

So I was wondering if there was a similar command with Incus?


* As a slight aside, this in fact proved to be useful after the migration!

I noticed I’d lost internet access to my containers after migrating to Incus, and spotted the problem when looking at the backed up lxd init --dump file.

The backed up config showed the following in Profiles>Devices section.

      name: eth0
      nictype: bridged
      parent: br0
      type: nic

And looking at my one in-use profile in Incus, it had this content.

      name: eth0
      network: incus
      type: nic

I’m doing this from memory, the network key/value might be off, but the takeaway is that it had deleted, or not copied over, my bridge setup.

In any case, this is just an aside. If it looks like a bug I’d be happy to submit it, or if it’s expected behaviour then no worries :slight_smile:

incus admin init --dump

1 Like