DinD deployment cannot connect to the Docker daemon
Error recorded 2 times in PanelAlpha Engine deploys on Express, Fallback. 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.
Seen2 times · 2 variants
WhereExpress, Fallback
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The deployment reached the run stage, but the account’s nested Docker environment could not access /var/run/docker.sock. The Docker daemon or socket is missing, unavailable, or not mounted into the deployment environment. The build log also shows a missing file under server/node_modules, which may require cleanup before retrying.
What the log looks like
Deploy log
#25 ERROR: failed to copy files: failed to open source .../app/server/node_modules/jest-circus/node_modules/@<b64>.d.ts: no such file or directoryERROR: failed to build: failed to solve: failed to copy files...failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directoryCould not pre-pull nginx:alpine