I'm now seeing the same problem that was reported on the (now archived) ubuntu-wsl2-systemd-script:
DamionGans/ubuntu-wsl2-systemd-script#15
The solution is to add the following to /etc/rc.local in step 6
ls /proc/sys/fs/binfmt_misc > /dev/null 2>&1 || \
mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc
More background:
Without this fix, I am now seeing the following when attempting to debug an application created using create react app:
[client] Error: spawn WSL Interopability is disabled. Please enable it before using WSL.
[client] C:/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe ENOENT
[client] at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
The error message itself is produced by wslu-header when it is not able to verify that binfmt_misc/WSLInterop is enabled. Googling on that lead me to ubuntu-wsl2-systemd-script issue and ultimate fix.
Apparently, invoking the webpack devserver causes the system default browser to be launched, which in the case of WSL2 involves spawning out to powershell.
I'm now seeing the same problem that was reported on the (now archived) ubuntu-wsl2-systemd-script:
DamionGans/ubuntu-wsl2-systemd-script#15
The solution is to add the following to
/etc/rc.localin step 6More background:
Without this fix, I am now seeing the following when attempting to debug an application created using create react app:
The error message itself is produced by wslu-header when it is not able to verify that
binfmt_misc/WSLInteropisenabled. Googling on that lead me to ubuntu-wsl2-systemd-script issue and ultimate fix.Apparently, invoking the webpack devserver causes the system default browser to be launched, which in the case of WSL2 involves spawning out to powershell.