Troubleshooting a container that won't start
When you deploy your Docker stack with Cloud 66, the containers created from your image may have issues starting, and this guide will walk you through how to troubleshoot this. You should ensure that your containers run in development before deploying with Cloud 66, as this will avoid the most common issues.
Use LiveLogs from your stack page on Cloud 66 to check the logs from your containers. The
<service>_start_errors.log logs should provide enough information to help you figure out why the container can’t start.
Troubleshooting a container that has started
If your container has started, but isn’t outputting the expected results, you can follow these steps to troubleshoot.
Use LiveLogs to check the log output from your containers.
Use the toolbelt to exec into the given container to troubleshoot:
cx containers exec -s <stack> <container_id> /bin/bash
This command executes your command within the context of a running container. Once you’re inside the container, you’ll be able to verify why the server isn’t running as expected.