You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a practical deployment guide for Windows + Docker Desktop environments, covering real-world issues encountered during local setup.
What's included
Pre-requisites: Docker Desktop configuration for corporate-managed Windows endpoints (IP-Guard, WSL restrictions, Hyper-V fallback)
5 critical config fixes before first launch:
Root .env setup (BETTER_AUTH, API keys)
config.yaml model configuration
Removing sensitive volume mounts that crash Docker on managed endpoints
next.config.js patch to bypass TypeScript/ESLint build errors
frontend/.env and extensions_config.json initialization to prevent 500 errors
BuildKit manifest list issue (root cause analysis + fix): docker compose up fails with No such image because BuildKit stores OCI manifest lists in its own cache instead of the Docker daemon's image store — workaround using docker build + --pull never
Docker context isolation on Windows (default vs desktop-linux)
Quick-reference redeployment commands
Environment tested
OS: Windows 10 Enterprise LTSC (corporate managed)
Hi, I've updated the troubleshooting guide with an additional fix.
New section added: "502 Bad Gateway — gateway startup failure"
Root cause: The .env file contains Windows-style paths (e.g., D:\hical\deer-flow\config.yaml) for DEER_FLOW_CONFIG_PATH and DEER_FLOW_EXTENSIONS_CONFIG_PATH. These are passed into the container via env_file, but the Linux process inside the container cannot resolve Windows paths, causing the gateway to fail at startup and nginx to return 502.
Fix: Explicitly override these two variables with container-internal paths in the docker-compose.yaml gateway environment block, which takes precedence over env_file.
This is a common pitfall for Windows users deploying with Docker Desktop. The updated doc now includes the full diagnosis steps and fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a practical deployment guide for Windows + Docker Desktop environments, covering real-world issues encountered during local setup.
What's included
.envsetup (BETTER_AUTH, API keys)config.yamlmodel configurationnext.config.jspatch to bypass TypeScript/ESLint build errorsfrontend/.envandextensions_config.jsoninitialization to prevent 500 errorsdocker compose upfails withNo such imagebecause BuildKit stores OCI manifest lists in its own cache instead of the Docker daemon's image store — workaround usingdocker build+--pull neverdefaultvsdesktop-linux)Environment tested