Python app restarts because Gunicorn fails to import the application
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 running but does not answer on the port it publishes. app listens on 39879, not on 8095. Its output is in the deploy log, or read it with container_service_logs.
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.
Seen6 times
WherePython
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, but the Gunicorn process exits while loading the application. Because it keeps restarting, port 8000 never answers the health check. The final import error is not included in the available log excerpt, so the specific startup cause is unclear.
What the log looks like
Deploy log
Starting application (docker compose up -d)Container project-app-1 StartedHealth check: http://[ip]:8000/ did not answer — Failed to connect to [ip] port 8000Check failed: The application is restarting, not runningapp-1 | ... gunicorn/app/wsgiapp.py ...app-1 | return util.import_app(self.app_uri)app-1 | ... importlib.import_module(module)