Troubleshooting Airbyte on GCP VM with Docker containers

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is facing issues with Airbyte deployment on GCP VM, where extra BigQuery containers are running alongside Airbyte containers, causing a potential hung state. The user is seeking guidance on debugging errors and accessing specific Docker logs for troubleshooting.


Question

I’ve deployed Airbyte on GCP, but after a few days, it stopped working. Upon inspecting the running Docker containers, I noticed that there are three BigQuery containers running alongside other Airbyte containers for the past five days, which shouldn’t be the case. It appears that Airbyte might be stuck in a hung state. How can I debug errors on the GCP VM? I attempted to view the Docker logs for the container, but it’s mixing all the services together. Is there any documentation available to help me troubleshoot the issue with Airbyte hosted on the VM?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["troubleshooting", "airbyte", "gcp-vm", "docker-containers", "debugging", "documentation"]
2

Are there any connectors syncing? It’s normal to have a source and destination container (plus an orchestrator one when deploying via Kubernetes) for each active connector—this is just how Airbyte works.

If you need logs for just a single container, you can use:
docker container list
. . . followed by:
docker logs [CONTAINER NAME]

(you can also pair with --tail to just get the end of the log or --since and --until to get a certain time range)