On Windows, start the stack in Ubuntu

---

Native Windows can inspect. It cannot start the stack. The start path is Ubuntu on WSL2, in the Ubuntu shell, not in PowerShell and not in cmd.

Docker has to be Linux containers, with WSL2 integration on. If flisk doctor says the daemon is using the Windows engine, that is the fix it already printed. Switch the engine. Do not keep typing flisk up at the same prompt.

The path in the docs

Run this in Ubuntu. The first command copies the bundled example into your home directory. The second configures that copy.

flisk doctor
flisk project example --path "$HOME/tdk-example"
cd "$HOME/tdk-example"
flisk project --yes
sed -i 's/^INFISICAL_ENABLED=.*/INFISICAL_ENABLED=false/' .env
flisk config verify
flisk doctor
flisk up shop

Leave flisk up shop running. Use a second Ubuntu terminal for curl. Set HTTP_PORT to the port that flisk up printed. That is 80 when port 80 is free, and 8080 on WSL2 when it is not. Do not assume 80 because a Mac screenshot showed 80.

The repo has a smoke test that does the same shape: copy the example, doctor, verify, boot, hit the routed write, watch the worker, tear the stack down. If your manual run cannot create an order and see the worker mark it, you do not have the example running. You have a container that happened to start.

What people skip

sed turns Infisical off in that example's .env. Skip it and the boot is waiting on a secrets tool you did not mean to use.

flisk config verify before the second doctor is there because a hand-edited generated file should fail before Tilt does. If verify fails, regenerate. Do not "fix" the Tiltfile in the Ubuntu home directory and call that a Windows bug.

Files written from Windows onto the Linux filesystem, or the other way around, are a WSL problem, not a Flisk feature. Keep the repo in the Linux home directory if the bind mounts look empty.

WSL2 notes

flisk.sh