You can use wsl.exe from powershell to manage wsl.
FWIW I started reverse engineering the WSL2 API -- it's not terribly complicated to do most tasks without the CLI (which is clunky IMO, as it had a number of times where it changed in backwards/forwards incompatible ways)
https://crates.io/crates/wsl-api
alt Hacker News
FWIW I started reverse engineering the WSL2 API -- it's not terribly complicated to do most tasks without the CLI (which is clunky IMO, as it had a number of times where it changed in backwards/forwards incompatible ways)
https://crates.io/crates/wsl-api