Compose deployment failed because a container kept restarting
Error recorded 111 times in PanelAlpha Engine deploys on Docker Compose, Django, Dockerfile and more. 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.
Seen111 times · 16 variants
WhereDocker Compose, Django, Dockerfile +12 moreDocker Compose, Django, Dockerfile, Express, Fallback, Go, Java, Laravel, Nextjs, Php, Python, Railpack, Rails, Rust, Vite
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Compose project started, but one container entered a restart loop before the proxy could reload. The log does not identify the container or its underlying error. No environment variables were supplied, so missing configuration is one possible cause.
What the log looks like
Deploy log
Starting stage: runningDetected project type: Docker ComposeUsing strategy: composeDetected application port: 80Webserver reload after proxy rules failed: Error response from daemon: Container <hex> is restarting, wait until the container is runningUsing default environment variables (source: none)Deploy failed: Error response from daemon: Container <hex> is restarting, wait until the container is running