Windows WSL setup

The ppl CLI requires a Linux environment. On Windows you run it inside WSL2 (Windows Subsystem for Linux 2), which gives you a real Linux kernel and native filesystem performance with zero virtualization overhead.

Before you start

Disable VPN (temporarily)

Some corporate VPNs block WSL's internet, which fails the CLI install. Disable the VPN for the install and re-enable it afterward.

Enable hardware virtualization

WSL2 requires hardware virtualization. Most modern PCs have it enabled by default — verify in Task Manager → Performance → CPU → Virtualization.

If it says Enabled, you're good. If Disabled:

  1. Restart your PC and press the BIOS key during boot (Lenovo: F1/F2/Fn+F2, Dell: F2, ASUS: Del/F2).
  2. Find Virtualization Technology, VT-x, or AMD-V and set it to Enabled.
  3. Save and exit. After reboot, re-check Task Manager.

Video: How to enable virtualization in Lenovo BIOS. Other brands have similar menus.

Install WSL2 with Ubuntu

Open PowerShell as Administrator and run:

wsl --install

This installs WSL2 plus Ubuntu by default. Restart when prompted. After reboot, Ubuntu finishes setup and asks you to pick a username and password — these are independent of your Windows account.

Update Ubuntu

Launch Ubuntu from the Start menu and run:

sudo apt update && sudo apt upgrade -y

Install the CLI

Inside the Ubuntu terminal:

curl -fsSL https://app.pipelogic.ai/api/v1/install | bash

The installer downloads the right binary for your platform, verifies its checksum, and symlinks ppl into $HOME/.local/bin. If that directory isn't already on your PATH, the installer prints the exact line to add for your shell (for example, appending export PATH="$HOME/.local/bin:$PATH" to ~/.bashrc). Add it, then reopen the terminal.

Verify

ppl version
ppl

If you see command not found: ppl, your shell hasn't picked up the new PATH — close and reopen the Ubuntu terminal.

Start using the CLI

ppl login
ppl runtime list
ppl component list

For exact command syntax, run ppl <command> --help.

Notes

  • The install command must be run inside the Ubuntu (WSL) terminal, not in Windows CMD or PowerShell.
  • File paths inside WSL look like /home/<user>/... — Windows paths (C:\Users\...) work via /mnt/c/Users/....
  • Component builds run remotely on the platform — no local Docker or build toolchain is needed inside WSL.

Was this page helpful?