Run sdme inside WSL 2 on Windows.
sdme requires Linux with systemd. On Windows, use WSL 2, which runs a real Linux kernel; current Ubuntu WSL images boot systemd by default.
From an elevated PowerShell:
wsl --install
This installs WSL and Ubuntu. Reboot if prompted.
Start the distro:
wsl
Verify systemd is running:
systemctl is-system-running
If it reports that systemd is not running, add the following to /etc/wsl.conf inside WSL:
[boot]
systemd=true
Then restart WSL from PowerShell with wsl --shutdown and start it again.
Inside WSL:
curl -fsSL https://sdme.io/install.sh | sudo sh
Verify the installation:
sdme --version
All sdme commands run inside WSL from this point.
PowerShell aliases cannot embed arguments, so add a function to your PowerShell profile instead (open it with notepad $PROFILE):
function sdme { wsl sudo sdme @args }
This lets you run commands like sdme new, sdme join, sdme ps, and sdme stop directly from the Windows prompt. Filesystem operations such as fs import, fs build, cp, and fs export also work through the wrapper, since WSL maps the Windows working directory to a writable /mnt/<drive> path.
/mnt/c and friends via drvfs. Bind mounts (-b) pointing there work, but file operations are slower than in the WSL filesystem; keep heavy import, export, and build data inside the WSL home for best performance.localhost from Windows through WSL's localhost forwarding. Private-network containers require additional port forwarding, or mirrored networking mode on Windows 11.arm64/aarch64.