Python app restarts because its start command cannot run in the container
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.
Seen118 times
WherePython
StatusIn AnalysisOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The container exits at start: either the project virtualenv was built for a different Python than the runtime image, or the repository is a command-line tool with no web server.
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)