wsl-exec throws errors on launch with apostrophe in user's home path

[teandresmith]

Actual Behavior

When starting Rancher Desktop, there are errors when running wsl-exec script and application is stuck on "Initializing Rancher Desktop"

Steps to Reproduce

1. Have an apostrophe in your home path, e.g. in my case "C:\Users\Te'Andre.Smith"
2. Launch Rancher Desktop

Result

Last part of wsl-exec.log shows this:

2024-08-08T21:24:02.060Z: Running: wsl.exe --distribution rancher-desktop --exec /mnt/c/Users/TE'AND~1.SMI/AppData/Local/Temp/rd-install-k3s-XXXXXXoYJj1S/install-k3s v1.30.3+k3s1 /mnt/c/Users/Te'Andre.Smith/AppData/Local/rancher-desktop/cache/k3s
2024-08-08T21:24:02.562Z: Running: wsl.exe --distribution rancher-desktop --exec wslpath -a -u C:\Users\Te'Andre.Smith\AppData\Local\rancher-desktop\provisioning
2024-08-08T21:24:03.018Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service --ifstarted local stop
2024-08-08T21:24:03.467Z: Running: wsl.exe --distribution rancher-desktop --exec rm -r -f /etc/local.d
2024-08-08T21:24:03.905Z: Running: wsl.exe --distribution rancher-desktop --exec ln -s -f -T /mnt/c/Users/Te'Andre.Smith/AppData/Local/rancher-desktop/provisioning /etc/local.d
2024-08-08T21:24:04.375Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d/ ( -name *.start -o -name *.stop ) -print -exec chmod a+x {} ;
2024-08-08T21:24:04.839Z: Running: wsl.exe --distribution rancher-desktop --exec /sbin/rc-update --update
/lib/rc/sh/gendepends.sh: /etc/init.d/../conf.d/buildkitd: line 32: syntax error: unterminated quoted string

 * /etc/fstab does not exist
Service `hwdrivers' needs non existent service `dev'
 * Caching service dependencies ... [ ok ]
2024-08-08T21:24:05.298Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service --ifnotstarted local start
 * Starting local ... [ ok ]
2024-08-08T21:24:05.781Z: Running: wsl.exe --distribution rancher-desktop --exec /sbin/rc-update --update
/lib/rc/sh/gendepends.sh: /etc/init.d/../conf.d/buildkitd: line 32: syntax error: unterminated quoted string

 * /etc/fstab does not exist
Service `hwdrivers' needs non existent service `dev'
 * Caching service dependencies ... [ ok ]
2024-08-08T21:24:06.227Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service --ifnotstarted docker start
 * Starting Rancher Desktop Docker Daemon ...
 * supervise-daemon: Please increase the value of --respawn-period to more than 50 to avoid infinite respawning
 [ ok ]

wsl-helper show

Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 4FBB540F-1987-41D8-9486-54DDD21A3C67: could not dial Hyper-V socket: connect(4fbb540f-1987-41d8-9486-54ddd21a3c67:016a6eb7-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 4FBB540F-1987-41D8-9486-54DDD21A3C67: could not dial Hyper-V socket: connect(4fbb540f-1987-41d8-9486-54ddd21a3c67:016a6eb7-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 4FBB540F-1987-41D8-9486-54DDD21A3C67: could not dial Hyper-V socket: connect(4fbb540f-1987-41d8-9486-54ddd21a3c67:016a6eb7-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: could not detect WSL2 VM: could not find WSL2 VM ID: could not dial VM 4FBB540F-1987-41D8-9486-54DDD21A3C67: could not dial Hyper-V socket: connect(4fbb540f-1987-41d8-9486-54ddd21a3c67:016a6eb7-facb-11e6-bd58-64006a7986d3) failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

wsl-init show:

2024-08-08T21:23:57.003Z: + NETWORK_SETUP_LOG='/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/network-setup.log'
+ VM_SWITCH_LOG='/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/vm-switch.log'
+ '[' 436 -ne 1 ]
+ exec /usr/local/bin/network-setup --logfile '/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/network-setup.log' --vm-switch-path /usr/local/bin/vm-switch --vm-switch-logfile '/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/vm-switch.log' --unshare-arg /usr/local/bin/wsl-init
2024-08-08T21:23:57.552Z: + NETWORK_SETUP_LOG='/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/network-setup.log'
+ VM_SWITCH_LOG='/mnt/c/Users/Te'"'"'Andre.Smith/AppData/Local/rancher-desktop/logs/vm-switch.log'
+ '[' 1 -ne 1 ]
2024-08-08T21:23:57.552Z: + IFS=:
+ mount --make-shared /
2024-08-08T21:23:57.552Z: + mount --make-shared /etc/rancher
2024-08-08T21:23:57.553Z: + mount --make-shared /var/lib
2024-08-08T21:23:57.553Z: + mount bpffs -t bpf /sys/fs/bpf
2024-08-08T21:23:57.561Z: + mount --make-shared /sys/fs/bpf
2024-08-08T21:23:57.562Z: + mount --make-shared /sys/fs/cgroup
2024-08-08T21:23:57.563Z: + mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc
2024-08-08T21:23:57.564Z: + mount --make-shared /proc/sys/fs/binfmt_misc
2024-08-08T21:23:57.565Z: + '[' -f /var/lib/resolv.conf ]
+ exec /sbin/init
2024-08-08T21:23:57.569Z: 
2024-08-08T21:23:57.570Z:    �[1m�[32mOpenRC �[1m�[36m0.54�[m is starting up �[1m�[34mLinux 5.15.153.1-microsoft-standard-WSL2 (x86_64) [DOCKER]�[m
2024-08-08T21:23:57.575Z:  �[1m�[32m*�[m /proc is already mounted�[K
2024-08-08T21:23:57.580Z:  �[1m�[32m*�[m /run/openrc: creating directory�[K
2024-08-08T21:23:57.580Z:  �[1m�[32m*�[m /run/lock: correcting mode�[K
 �[1m�[32m*�[m /run/lock: correcting owner�[K
2024-08-08T21:23:57.582Z:  �[1m�[32m*�[m Caching service dependencies�[K ...
2024-08-08T21:23:57.589Z: /lib/rc/sh/gendepends.sh: /etc/init.d/../conf.d/buildkitd: line 32: syntax error: unterminated quoted string
2024-08-08T21:23:57.633Z:  �[1m�[31m*�[m /etc/fstab does not exist�[K
2024-08-08T21:23:57.662Z: Service `hwdrivers' needs non existent service `dev'
 [ ok ]
2024-08-08T21:23:57.705Z:  �[1m�[32m*�[m Starting busybox crond�[K ...
2024-08-08T21:23:57.708Z:  [ ok ]
2024-08-08T21:23:57.719Z:  �[1m�[32m*�[m Starting dnsmasq�[K ...
2024-08-08T21:23:57.821Z:  [ ok ]
2024-08-08T21:23:57.841Z:  �[1m�[32m*�[m Starting Rancher Desktop Guest Agent�[K ...
2024-08-08T21:23:57.842Z:  [ ok ]

Expected Behavior

Rancher Desktop should be able to handle apostrophes in the home path

Additional Information

No response

Rancher Desktop Version

1.15.0

Rancher Desktop K8s Version

1.30.3

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Microsoft Windows 10 Enterprise V10.0.19045 Build 19045

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

Cloudflare VPN

[jandubois]

See also #1943. Not sure if this is a duplicate, or if there is more than one issue with this.