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

​

Pending

If the container is in the Pending state after deployment, it has been created but is not yet running.

​

Deployment Failed

If the container is in the Deployment Failed state, check the Runtime Logs to identify the root cause. Common causes include:

• Invalid container image URL.
• Registry authentication failure.
• Invalid startup command.

​

Unhealthy

If the container is in the Unhealthy state, verify that the configured health check endpoint is responding correctly. Common causes include:

• Application startup failures.
• Incorrect port configuration.
• Invalid health check configuration.

​

Modify Container Settings

Most container settings can be modified only after the container has been stopped. The container name is the only setting that can be changed while the container is running. Before applying configuration changes, we recommend checking the current deployment status and endpoint health.

​

Related Documentation