Skip to main content

​
Introduction

Troubleshooting Docker Compose applications deployed through Edge Infrastructure Services involves checking several areas: the Compose Runtime application instance, SSH access to the runtime, Docker CLI output from inside the runtime, and application logs and events.

​
Prerequisites

​
Access the Compose Runtime via SSH

The Compose Runtime exposes an SSH interface over the air-gapped Ethernet port (typically eth2) so you can connect to it for debugging. To use SSH access, you need the username and password you configured when deploying the Compose Runtime. Warning: If you did not record your Compose Runtime credentials at deployment time, they are not recoverable through Edge Infrastructure Services or any other method. Losing these credentials requires a full reinstallation of the Compose Runtime. You can access the Compose Runtime using either of the following methods: Option 1: Edge View Use Edge View to establish an SSH connection directly to the air-gapped Ethernet port (eth2) of the Compose Runtime. See Edge View and Remote Access for setup instructions. Option 2: SSH from the node
  1. Enable SSH on the node.
  2. Locate the IP address of the node.
  3. Connect to the node using SSH.
  4. From the node, identify the IP address of the Compose Runtime on the air-gapped interface. The default IP address is 10.1.255.154.
  5. Connect from the node to the Compose Runtime using SSH on that IP address.

​
Debug with Docker CLI

Each Docker Compose application instance deployed through Edge Infrastructure Services is assigned a unique application ID. This ID maps directly to the Docker Compose project-name, which lets you use standard Docker Compose commands to inspect a specific application instance. To list all containers for a specific application instance, run the following command from inside the Compose Runtime (replacing <appid> with the application instance ID):
You can find the application instance ID on the application instance detail page in Edge Infrastructure Services.

​
View Logs and Events

​
View events

Application events record state transitions such as changes from Loading to Online or from Restarting to Online. To view events:
  1. In the sidebar, click Infrastructure > Workloads > Applications.
  2. Click the Compose application instance you want to inspect.
  3. On the detail page, click the Events tab.

​
View logs

Docker Compose applications produce logs for normal operations, errors and warnings, and debugging output. To view logs:
  1. In the sidebar, click Infrastructure > Workloads > Applications.
  2. Click the Compose application instance you want to inspect.
  3. On the detail page, click the Logs tab.

​
View Compose Runtime status

To view the runtime’s current state and inspect the agent, compose, and container runtime version information:
  1. In the sidebar, click Infrastructure > Workloads > Applications.
  2. Click the Compose Runtime application instance.
  3. On the Overview tab, verify the Run State and Uptime values.
  4. Look for the Runtime Platform Versions section on the detail page. This section shows the Compose App Instance Control agent version, the Docker Compose version, and the container runtime version.

​
Next Steps

This article is part of the Docker Compose setup series.
  1. Docker Compose Overview: background on the architecture and deployment model.
  2. Add a Compose Runtime Image: add the Compose Runtime image and create the Edge App bundle with network interfaces.
  3. Deploy the Compose Runtime Application: deploy the Compose Runtime as an application instance on your node.
  4. Attach an Existing ZFS Pool to the Compose Runtime: ZFS variant only. Configure the pool import and dataset discovery.
  5. Compose App Instance Control Overview: how the Compose Runtime manages Docker Compose application lifecycles.
  6. Add a Docker Compose Image: create the Docker Compose app image that runs inside the Compose Runtime.
  7. Deploy a Docker Compose Application: deploy the Docker Compose app as an application instance on the node that runs the Compose Runtime.
  8. Troubleshoot Docker Compose (you are here).