Go deploy fails to start because the deploy log is not writable
Error recorded 5 times in PanelAlpha Engine deploys on Go. The deploy log below is the recorded failure output.
TypeErrorAn 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.
Seen5 times · 2 variants
WhereGo
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Go image downloads successfully, but the startup wrapper then looks for Node.js lockfiles that are not present in this Go project. The final failure is obscured by a generic image-start error and a permission error while opening the log. The exact failing command is unclear from the available output.
What the log looks like
Deploy log
Starting stage: runningDetected project type: GoUsing strategy: goCompiling application on hostStatus: Downloaded newer image for golang:1.27-alpinecp: can't stat '/app/package-lock.json': No such file or directorycp: can't stat '/app/pnpm-lock.yaml': No such file or directoryERROR: Unable to open log: Permission deniedDeploy failed: Failed to start app: Unable to find image 'golang:1.27-alpine' locally