Colima fails to mount paths containing spaces

[wegotoeleven]

Description

Colima cannot mount paths that contain spaces, such as "/Volumes/External HD", even when properly quoted or escaped.

Version

❯ colima version && limactl --version && qemu-img --version
colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a

runtime: docker
arch: aarch64
client: v29.1.3
server: v28.4.0
limactl version 2.0.3

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

❯ colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] docker socket: unix:///Users/wegotoeleven/.colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/wegotoeleven/.colima/default/containerd.sock

Reproduction Steps

1. Mount an external disk
2. Change the name, ensuring there's a space (for example, /Volumes/External HD)
3. colima start --cpu 4 --memory 8 --disk 100 --mount "/Volumes/External HD:w"

Expected behaviour

The path should be mounted successfully into the VM, allowing Docker containers to access /Volumes/External HD.

In reality, the drive doesn't mount, as evidenced by:

❯ colima ssh
wegotoeleven@mantis:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        19G  1.3G   18G   7% /
tmpfs           5.9G     0  5.9G   0% /dev/shm
tmpfs           2.4G  712K  2.4G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
efivarfs         56K  2.1K   54K   4% /sys/firmware/efi/efivars
mount0          461G   37G  424G   8% /Users/wegotoeleven/Library/Caches/colima
/dev/vda16      891M   32M  797M   4% /boot
/dev/vda15       98M  6.4M   92M   7% /boot/efi
tmpfs           1.2G  4.0K  1.2G   1% /run/user/501
/dev/vdc         54M   54M     0 100% /mnt/lima-cidata
/dev/vdb1        98G  1.8G   92G   2% /mnt/lima-colima

Additional context

This is particularly problematic for macOS users where external drives often have spaces in their names by default (e.g., "External HD", "Backup Drive"). Would be helpful to either:

1. Support proper escaping/quoting of paths with spaces
2. Document this limitation clearly in the mount documentation (if it isn't already)