From 5bd99c10078d78f61ac8a0bb2f0e7acc6081e8b6 Mon Sep 17 00:00:00 2001 From: Connor Howington Date: Mon, 11 May 2026 10:11:33 -0500 Subject: [PATCH 1/2] Add fixes for DevPod issues on Windows --- docs/devpod.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/devpod.md b/docs/devpod.md index e9057f5..b820c49 100644 --- a/docs/devpod.md +++ b/docs/devpod.md @@ -29,6 +29,7 @@ The workspace uses the external image referenced there, which is expected to pro - If on Windows, edit the advanced options to specify the "Host" as `tcp://127.0.0.1:2375` and change "Docker Path" to "podman". 6. Select VS Code as your IDE 7. Click Create - the dev container will be pulled down and started for you, and VS Code should open + - If you have trouble with this step on Windows, see [Troubleshooting DevPod on Windows](#troubleshooting-devpod-on-windows) 8. After the workspace starts, open a terminal in VS Code and run ```bash uv sync --dev --all-extras @@ -149,3 +150,22 @@ You're all set! Now when you run the app locally, it will come up in your web br - If your DevPod or dev container image defines shell aliases that reference the placeholder project name, update that environment after renaming the project. - This workspace intentionally uses an external dev container image for fast startup. - The repo's Docker-based workflow is still available in [`docs/container.md`](docs/container.md) for building runnable images and the optional browser-served GUI (Xpra HTML) target. + +### Troubleshooting DevPod on Windows + +#### `podman` binary not found in `%PATH%` during DevPod workspace build + +Run in PowerShell to extend your path, replacing `[your user]` with your username: + +```PowerShell +[Environment]::SetEnvironmentVariable("PATH", $env:PATH + ";C:\Users\[your user]\.local\bin", "User") +``` + +#### VS Code fails to connect to running workspace with `Bad owner or permissions on C:\\Users\\[username]/.ssh/config` error in terminal + +Run in PowerShell to set the correct permissions for the SSH config folder: + +```PowerShell +icacls "$env:USERPROFILE\.ssh\config" /setowner "$env:USERNAME" +icacls "$env:USERPROFILE\.ssh\config" /inheritance:r /grant:r "${env:USERNAME}:(F)" +``` From 0581388ff9d12584ea53f90ceb583e1c544a97a0 Mon Sep 17 00:00:00 2001 From: Connor Howington Date: Mon, 11 May 2026 10:50:56 -0500 Subject: [PATCH 2/2] Add note about deleting .docker folder --- docs/devpod.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/devpod.md b/docs/devpod.md index b820c49..251f8fe 100644 --- a/docs/devpod.md +++ b/docs/devpod.md @@ -153,6 +153,8 @@ You're all set! Now when you run the app locally, it will come up in your web br ### Troubleshooting DevPod on Windows +After applying any of these fixes, be sure to fully stop Podman and DevPod (making sure their icons are not still present in the taskbar hidden icons menu) restart them, and then create a new DevPod workspace from scratch (starting from [step 4](#setup) above) + #### `podman` binary not found in `%PATH%` during DevPod workspace build Run in PowerShell to extend your path, replacing `[your user]` with your username: @@ -161,6 +163,8 @@ Run in PowerShell to extend your path, replacing `[your user]` with your usernam [Environment]::SetEnvironmentVariable("PATH", $env:PATH + ";C:\Users\[your user]\.local\bin", "User") ``` +Also try deleting any pre-existing `C:\Users\[your user]\.docker` folder, as this may interfere with the Podman configuration. + #### VS Code fails to connect to running workspace with `Bad owner or permissions on C:\\Users\\[username]/.ssh/config` error in terminal Run in PowerShell to set the correct permissions for the SSH config folder: