[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"problem-detail-error-go-deploy-fails-because-no-go-files-are":3},{"stack":4,"error":5,"seoName":6,"seoStack":7,"seo":8,"breadcrumb":10,"titlePrefix":17,"titleAccent":18,"lead":19,"facts":22,"why":37,"log":47,"fix":80,"engine":89,"related":97,"pitch":104},"go","go-deploy-fails-because-no-go-files-are","Go deploy fails because no Go files are found in \u002Fapp","Go",{"description":9},"Learn what causes Go deploy fails because no Go files are found in \u002Fapp, how PanelAlpha Engine responds to it during deployment.",[11,14,16],{"label":12,"href":13},"App Installations","\u002Fapps",{"label":7,"href":15},"\u002Fapps\u002Fstacks\u002Fgo",{"label":6},"Go deploy fails because ","no Go files are found in \u002Fapp",[20],{"text":21},"Error recorded 2 times in PanelAlpha Engine deploys on Go. The deploy log below is the recorded failure output.",[23,28,31,33],{"label":24,"value":25,"tone":26,"tooltip":27},"Type","Error","err","An error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.",{"label":29,"value":30},"Seen","2 times",{"label":32,"value":7},"Where",{"label":34,"value":35,"tooltip":36},"Status","Observed","Our team will look into this soon, verify the cause and try to fix it in an upcoming release.",{"heading":38,"body":39},"Why it happens",[40,42,45],{"text":41},"The Go strategy started compilation in ",{"text":43,"code":44},"\u002Fapp",true,{"text":46},", but no Go source files were available there. This usually means the build context or working directory does not match the repository layout, or the selected strategy is not suitable for this repository. A separate log-permission warning was also reported, but the deployment stopped on the missing Go files.",{"heading":48,"block":49},"What the log looks like",{"header":50,"lines":51},"Deploy log",[52,56,60,64,68,72,76],{"segments":53},[54],{"text":55},"Starting stage: running",{"segments":57},[58],{"text":59},"Detected project type: Go",{"segments":61},[62],{"text":63},"Using strategy: go",{"segments":65},[66],{"text":67},"Compiling application on host",{"segments":69},[70],{"text":71},"ERROR: Unable to open log: Permission denied",{"segments":73},[74],{"text":75},"no Go files in \u002Fapp",{"segments":77},[78],{"text":79},"Deploy failed: Failed to start app: no Go files in \u002Fapp",{"heading":81,"steps":82,"block":86},"How to fix it",[83],[84],{"text":85},"Inspect the repository and confirm where the Go entrypoint files are located. Update the compose or build configuration to use the correct build context and working directory, or provide the appropriate Dockerfile and start command. If the application is nested in a subdirectory, configure the deploy to build from that directory. Retry after confirming the required files are included in the checkout.",{"header":87,"lines":88},"Fix by hand",[],{"heading":90,"body":91,"block":94},"How PanelAlpha Engine solves it",[92],{"text":93},"The Go strategy should verify that Go source files exist in the selected build directory before compiling, and report the resolved build context and working directory. The log permission error should be surfaced separately from the primary build failure.",{"header":95,"lines":96},"",[],{"heading":98,"items":99},"Apps affected",[100],{"title":101,"badge":102,"tone":26,"href":103},"envoy","2 occurrences","\u002Fapps\u002Fenvoyproxy\u002Fenvoy",{"heading":105,"body":106,"footNote":107,"docsLabel":108,"docsHref":109},"Try PanelAlpha Engine yourself.","The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.","Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPU","Read the documentation","https:\u002F\u002Fpanelalpha.com\u002Fdocs"]