Nuxt app restarts because its users file cannot be initialized
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) 28 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.
Seen1 times
WhereNuxt
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Nuxt build completes, but the application exits during startup and enters a restart loop. It cannot find the example users file at /app/.examples/users.json, so it cannot create /tmp/.clyo/users.json. The health check then fails because nothing remains listening on port 3000.
What the log looks like
Deploy log
Application compiledStarting application (docker compose up -d)Health check: http://[ip]:3000/ did not answer — Failed to connect to [ip] port 3000app-1 | Users file not found, copying example file...app-1 | Source example file does not exist: /app/.examples/users.jsonapp-1 | Fatal: Users file could not be initialized at /tmp/.clyo/users.jsonapp-1 | ...container restarting...