doc: List image formats supported by incus-migrate

gibmat · gibmat · commit 010e617f3f25 · 2024-09-13T16:27:51.000-06:00
Signed-off-by: Mathias Gibbens &lt;mathias.gibbens@futurfusion.io&gt;
diff --git a/doc/.sphinx/.markdownlint/exceptions.txt b/doc/.sphinx/.markdownlint/exceptions.txt
@@ -1,5 +1,5 @@
-.tmp/doc/howto/import_machines_to_instances.md:104: MD034 Bare URL used
-.tmp/doc/howto/import_machines_to_instances.md:208: MD034 Bare URL used
+.tmp/doc/howto/import_machines_to_instances.md:106: MD034 Bare URL used
+.tmp/doc/howto/import_machines_to_instances.md:210: MD034 Bare URL used
 .tmp/doc/howto/network_forwards.md:52: MD004 Unordered list style
 .tmp/doc/howto/network_forwards.md:56: MD004 Unordered list style
 .tmp/doc/howto/network_forwards.md:53: MD005 Inconsistent indentation for list items at the same level
diff --git a/doc/howto/import_machines_to_instances.md b/doc/howto/import_machines_to_instances.md
@@ -7,6 +7,8 @@ You can run the tool on any Linux machine.
 It connects to an Incus server and creates a blank instance, which you can configure during or after the migration.
 The tool then copies the data from the disk or image that you provide to the instance.
 
+`incus-migrate` can import images in `raw`, `qcow2`, and `vmdk` file formats.
+
 ```{note}
 If you want to configure your new instance during the migration process, set up the entities that you want your instance to use before starting the migration process.
 
