Troubleshooting

If you encounter issues after deploying a container, follow the steps below to identify and resolve the problem.

​

Check Runtime Logs

If a deployment fails or behaves unexpectedly, Runtime Logs are the best place to start. You can view logs in real time or download them for further analysis.

​

Common Checks

Before investigating further, verify the following:

• The container image URL is correct.
• Registry credentials are valid for private registries.
• The configured port matches the application’s listening port.
• The startup command is correct.
• The health check endpoint responds successfully.
• All required environment variables are configured.

​

Check the Container Status

​

READY

The container has been created but is not running. Click Start Container to run it. Containers in READY are not billed.

​

DEPLOY FAILED

Open the Error Details chip next to the status. It names the diagnosed cause and what to do about it — see Deployment Error Codes for the full list. The dialog also links straight to the container’s runtime logs. Common causes include:

• Invalid container image URL.
• Registry authentication failure.
• Invalid startup command.
• Requested resources exceeding what the device can provide.

Containers in DEPLOY FAILED are not billed.

​

UNHEALTHY

The container is running but failing its health checks. Error Details is available here too. Common causes include:

• Application startup failures.
• Incorrect port configuration.
• Invalid health check configuration — for a slow-loading model, raise the health check timeout.

Containers in UNHEALTHY are not billed.

​

Container Won’t Start

If the container stays in READY or takes a long time to deploy, the GPU may have no free capacity. Check the availability badge on the GPU, and see GPU Availability and Limits — you can join the waitlist or pick another GPU.

​

Modify Container Settings

Most container settings require the container to be stopped. Exceptions are the container name, the replica count, and the persistent volume size, which can be changed while it runs. Before applying configuration changes, we recommend checking the current deployment status and endpoint health.

​

Related Documentation