The image writes where it may not here

What it means

Containers here run without root and with a read-only file system: only /home/container and /tmp are writable.

The build passed, but the app did not start or did not answer the health check.

Typical causes

• The app does not listen on 0.0.0.0 and the port from the PORT variable
• An environment variable is missing, or the database or Redis is not connected
• The start command is wrong or the process exits right away

How to fix it on mevcore

If the image allows it, move its data to /home/container with environment variables. All-in-one images that start their own database and nginx as root (such as AzuraCast) do not work here: they need a server of their own.

1. 1 Open the app in the mevcore panel: the Problems card on the overview shows this error and the log line it was found in.
2. 2 After the fix, deploy again. If it fails again, the log ends with [mevcore] lines naming the new error code.
3. 3 The "Ask AI" button next to the error prepares a request for ChatGPT or Claude: the error code, the end of the log without secrets and the app settings.

For an AI assistant

The same in English: paste it together with the log into the AI chat.

mevcore error code: runtime.outside_writable
phase: start / health check
diagnosis: The image writes where it may not here
platform hint: Containers here run without root and with a read-only file system: only /home/container and /tmp are writable. If the image allows it, move its data to /home/container with environment variables. All-in-one images that start their own database and nginx as root (such as AzuraCast) do not work here: they need a server of their own.
platform docs: https://mevcore.com/llms-full.txt