fyi on a flyte dev bug issue I hit. Claude says it's a bug. I haven't confirmed but thought you could check The devbox is retrying now with the fix in place. Quick recap of what happened: The failure:

flyte start devbox

died at the "Starting container" step with

docker: Error response from daemon: \tmp\.kube is not a valid Windows path

. The cause: a Windows bug in the Flyte SDK itself — _devbox.py hardcodes

/tmp/.kube

as the host directory it bind-mounts into the devbox container for the k3s kubeconfig. On Windows that renders as

\tmp\.kube

with no drive letter, which Docker rejects. The fix: I patched the installed copy in your venv so that on Windows it uses your real temp directory (

%TEMP%\flyte-devbox-kube

) instead; behavior on Linux/macOS is unchanged. Two caveats worth knowing: • This patch lives in`.venv`— if you ever reinstall or upgrade the`flyte`package, it'll be overwritten. It's a legitimate upstream bug in`flyte`2.5.14, worth filing on the flyte repo (I can draft that issue if you want). • You don't have`kubectl`on PATH as far as I've seen, so the launcher will print a warning and skip the kubeconfig merge — that's fine; it's only needed if you want to poke at the k3s cluster directly, not for deploying pipelines. The first start pulls the full devbox image (several GB), so it'll take a few minutes. I'll pick it back up when it finishes — next steps after that are confirming the UI at localhost/v2 is up, then the cluster secrets (

github-token

,

anthropic-api-key

) and deploy, which will need tokens from you.

Amazing ! I faced a lot of overhead on setting up devbox. But I did the reverse engineer root setup by reading their deployments on github I deployed individual components on my cluster first via IaC i.e rustfs, postgres and knative and then linked the flyte binary helm chart accordingly. This removed the overhead for using devbox for me, required some service account fixes but overall it was sweet and very smooth setup. Highly recommend everyone to do it the above way because you get a lot of control over your setup !

Thank you @fierce-magician-24790! I've passed this off to the Flyte team. Great having you at the hack night!

Hi @fierce-magician-24790, Thanks for sharing! I’ve actually been following this issue as well, and it turns out the team just merged a fix upstream in PR #1399. I tested setting up the devbox on Windows with the update, and it worked smoothly without hitting that path error.