Service Run Troubleshoot

Within this section you will find the common errors you might encounter when running your services with Qovery

My app is crashing, how do I connect to investigate?

Goal: You want to connect to your container's application to debug your application

First, try to use qovery shell command from the Qovery CLI. It's a safe method to connect to your container and debug your application.

If your app is crashing in the first seconds, you'll lose the connection to your container, making the debug almost impossible, then continue reading.

Your app is crashing very quickly, here is how to keep the full control of your container:

  1. Temporary delete the application port from your application configuration. This to avoid Kubernetes to restart the container when the port is not open.

  2. Into your Dockerfile, comment your EXEC or ENTRYPOINT and add a way to make your container sleep. For example:

    #CMD ["npm", "run", "start"]
    CMD ["tail", "-f", "/dev/null"]

    Commit and push your changes to trigger a new deployment (trigger it manually from the Qovery console if it's not the case).

  3. Once the deployment done, you can use qovery shell command to connect to your container and debug.

I can't access my application logs

If you are deploying a helm service, to get all the Qovery features (access your container logs, apply the stop/restart actions, display the pod status in the overview page), make sure to create an override and assign the macros qovery.labels.service and qovery.annotations.service to the labels and annotations of any deployed Pods/Deployments/Services/Jobs.

Override example:

mylabel: "test"

These macros will be automatically replaced by Qovery during the deployment phase.