-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect to API using fresh docker on GCE #30107
Comments
I have this issue with the api-server :( |
I've tried in 50.0.27 now with same issue except it takes 150s to timeout instead of the 20s. I turned debug on and went through logs on the docker in windows (WSL2) version and the ubuntu docker. Both are running docker 5.0.24 underneath. The API (:8006/v1/workspaces) is working under windows, but not under ubuntu. I've tried debian 10 as well in line with the instructions for GCE/Docker on the site. Here's what I've found so far. On the working version I see all the API routes getting added. I don't see this on the linux non-working version.
|
Here are the logs after a curl -x GET on /v1/workspaces The working version calls the list_paginated endpoint after the first response. Windows (works):
Linux (not working):
|
This is fixed now in latest release |
For anyone following this, some configs need updating due to the last release. I've documented them here: #29506 |
Topic
api docker
Revelant information
VERSION=0.50.24
I've followed the instructions at https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine/ and can't get the API to work. I can connect to the UI, create connections, sources, destinations, so obviously the internal API is working, but I can't get any results out of the API.
I've tried with debian 10, 11 and ubuntu 22.04 LTS underlying dockers same scenario.
If I run a GET http://localhost:8006/v1/workspaces, it responds after ~20 seconds with a 500 error. I've tried curl from the airbyte-api-server docker console too and get the same problem. It looks like maybe connectivity error from the airbyte-api-server to the airbyte-server dockers?
Example with new API (doesn't work - returns 500):
curl -u airbyte:password --request GET http://localhost:8006/v1/workspaces --header 'accept: application/json' {"type":"about:blank","status":500}
Example with config API (works):
curl -u airbyte:password --request POST http://localhost:8000/api/v1/workspaces/list --header 'accept: application/json' {"workspaces":[{"workspaceId":"6446bfdb-f5f7-420c-9757-5ab5c02ed02d","customerId":"67759121-5171-43c8-806f-fee1c8c5956c","name":"6446bfdb-f5f7-420c-9757-5ab5c02ed02d","slug":"6446bfdb-f5f7-420c-9757-5ab5c02ed02d","initialSetupComplete":false,"displaySetupWizard":true,"notifications":[],"notificationSettings":{},"defaultGeography":"auto","organizationId":"00000000-0000-0000-0000-000000000000"}]}
In the logs I see:
I'm following the instructions without any modifications to the docker-compose scripts. Only difference is I needed to run the first command as sudo (sudo bash run-ab-platform.sh)
The exact same docker scripts work fine when running on Docker Desktop on Windows. Maybe something to do with differences between networking on docker windows and docker linux?
Earlier up I see some errors in the airbyte-api-server logs, but I saw these on Windows too and it still worked there so not sure if it's relevant.
Any ideas?
The text was updated successfully, but these errors were encountered: