Check the application startup process
After you migrate application configurations by using Kompose or manually, you can check whether the application starts as expected in the Container Service for Kubernetes (ACK) console. If any exceptions occur during the startup process, you can analyze the boot log of the application in the console to locate the causes.
- Log on to the ACK console. In the left-side navigation pane, choose . Select the ACK cluster and namespace of the application that fails to start, find the application, and click Details in the Actions column.
- Click the Pods tab, find the container that runs the application and choose in the Actions column.
- On the Container Log page, view the log data.
Fix application startup issues
Analyze and fix application startup issues successively. For example, the preceding figure shows that the cause of the failure is that the application auth-service cannot access the config of the domain name . To fix this issue, perform the following operations:
- Manually create a service in the ACK cluster to allow other applications to access the config application. In the following figure, the field marked with 2 represents the service name. The service name must be the same as hostname. You can configure other settings based on your requirements, such as port mapping. You can set the Name and Service Port parameters to the same values that are specified for Container Port. For more information, see Create a service.
- After the container is redeployed, check whether the issue is fixed. If the state of the container is Running, it indicates that the container is started.
Some exceptions may occur during the application startup process. For more information about these exceptions and how to handle them, see Troubleshooting.