Laravel deploy completes, but the Node service keeps restarting
The application is restarting, not running. Docker reports tianji (running, last exit 0, restarted 1 time). It may answer between restarts, but it does not stay up. Read the container output with container_service_logs; the reason it exits is there. A process that exits 0 is restarted too, e.g. a command ending in a shell with no TTY.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen35 times · 3 variants
WhereDocker Compose, Dockerfile, Laravel
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Laravel application built and is reachable on port 8000, but the node dependency from Docker Compose is restarting. This leaves the deployment only partially usable: pages that depend on that service may fail. The available telemetry does not include the Node container’s underlying error.
What the log looks like
Deploy log
Detected project type: LaravelUsing strategy: laravelKeeping runtime services from compose: db, node...Detected application port: 8000Application health check: HTTP 302Docker reports node — it keeps restartingDependency health: failed