Dockerfile app restarts because SQLite cannot open its database
The application started but did not answer on any port it publishes. The deploy log has the per-port result; a worker or queue-only app can ignore this. | The application is restarting, not running. Docker reports app (Restarting (1) 26 seconds ago). Nothing answered on any published port because the process keeps exiting. Read the container output with container_service_logs; the reason it exits is there.
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.
Seen501 times · 12 variants
WhereDocker Compose, Django, Dockerfile +9 moreDocker Compose, Django, Dockerfile, ASP.NET, Express, Go, Java, Laravel, Node.js, Php, Railpack, Rust
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The container starts on port 8000 but exits during Django database access. SQLite is configured at /db/<account>.sqlite, and that path is missing or not writable by the application user. The restart loop prevents the health check from receiving a response.
What the log looks like
Deploy log
app-1 | 🐘 Database URL is: sqlite:////db/<account>.sqliteapp-1 | sqlite3.OperationalError: unable to open database fileapp-1 | ...app-1 | 🚀 Production webserver installed. Will run on port 8000app-1 | container status: Restarting