Storage troubleshooting for slicer mac

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

docs/mac/linux-vm.md

@@ -64,7 +64,7 @@ slicer vm shutdown slicer-1
 slicer vm exec slicer-1 -- sudo shutdown -h 0
 ```
 
-If your VM crashes or you kill slicer-mac without letting it shut down the VMs gracefully, you may need to check the disk image, which you can do via the [Troubleshooting](/mac/troubleshooting) page.
+If your VM crashes or you kill slicer-mac without letting it shut down the VMs gracefully, you may need to check the disk image. See [Check or repair a VM disk image](/mac/troubleshooting/#check-or-repair-a-vm-disk-image).
 
 If you ever want to "reset" your `slicer-1` VM, you can delete it and then relaunch it.
 

docs/mac/overview.md

@@ -70,6 +70,8 @@ In a similar way, a sandbox such as `sbox-1` may have K3s installed, exposing po
 
 Slicer for Mac uses Apple's [VZNATNetworkDeviceAttachment](https://developer.apple.com/documentation/virtualization/vznatnetworkdeviceattachment). Guests access the Internet through your host.
 
+If you also run Docker Desktop on the same Mac, configure it to use `Docker VMM` mode to avoid networking conflicts with Slicer. See [Use Docker from macOS with the Slicer VM socket](/mac/docker).
+
 * The host can ingress to guests using their IP or `slicer vm forward`
 * Guests can talk to the host to access things like HTTP proxies, or a Docker pull-through cache, etc.
 * Unlike Slicer for Linux, which supports bridged mode networking, guests on Slicer for Mac cannot talk to each other, unless you install an overlay network using something like Wireguard, routing through the host.

docs/mac/storage.md

@@ -56,18 +56,4 @@ rm -f ./slicer-1.img
 
 ## Troubleshooting
 
-If your VM crashes for some reason, or the Mac's sleep mode causes an issue with the VM, you may find the `.img` file needs to be checked or repaired with the `e2fsck` utility.
-
-Check the filesystem (read-only, no changes):
-
-```bash
-e2fsck -v -n ./slicer-1.img
-```
-
-If errors are found, repair them:
-
-```bash
-e2fsck -f ./slicer-1.img
-```
-
-You can obtain `e2fsck` by installing the `e2fsprogs` package via `brew install e2fsprogs`. Brew is available separately at: [https://brew.sh/](https://brew.sh/).
+If a VM disk image needs checking or repair, see [Check or repair a VM disk image](/mac/troubleshooting/#check-or-repair-a-vm-disk-image).

docs/mac/troubleshooting.md

@@ -1,8 +1,33 @@
 # Troubleshooting Slicer for Mac
 
+## Check or repair a VM disk image
+
+If your VM crashes, the Mac sleeps at the wrong time, or `slicer-mac` is killed before the guest shuts down cleanly, the VM disk image may need a filesystem check.
+
+Check the filesystem first in read-only mode:
+
+```bash
+e2fsck -v -n ./slicer-1.img
+```
+
+If errors are found, repair them:
+
+```bash
+e2fsck -f ./slicer-1.img
+```
+
+You can install `e2fsck` on macOS via Homebrew:
+
+```bash
+brew install e2fsprogs
+```
+
 ## No Internet or LAN access from the VM
 
 One failure mode on macOS is that the VM networking gets stuck on the wrong subnet because the host-side vmnet state becomes stale.
+
+If you also run Docker Desktop, first check that it is using `Docker VMM` mode. That is the supported way to run Docker and Slicer together without subnet conflicts. See [Use Docker from macOS with the Slicer VM socket](/mac/docker).
+
 You may notice one or more of the following:
 
 - `slicer vm list` shows `slicer-1` on `192.168.64.2`, but the VM cannot reach `192.168.64.1`