https://linen.dev logo
Join Slack
Powered by
Trying to install Airbyte in GCP for testing out a...
# ask-ai
k
Trying to install Airbyte in GCP for testing out a new ELT pipeline. I've installed Airbyte before in GCP for proof-of-concept type purposes. Followed the directions on Airbyte's website for deploying on GCP VMs before just fine, but this time around I'm running into this error when running 
docker compose up -d
. 
parsing /home/xxxxxxxxxx/airbyte/docker-compose.yaml: Non-string key at top level: 404
k
A message from kapa.ai
New message text here
k
run airbyte from a docker image? @kapa.ai
k
A message from kapa.ai
Sorry @Kevin Ruprecht, I am experiencing especially high traffic right now, please try again. 🧑‍💻
k
run airbyte from a docker image? @kapa.ai
k
A message from kapa.ai
To run Airbyte from a Docker image, follow these two steps: 1. Install Docker on your workstation. Make sure you're on the latest version of 
docker-compose
. You can find the installation instructions [here](https://www.docker.com/products/docker-desktop). 2. Run the following commands in your terminal to clone the Airbyte repository and start the platform:
Copy code
bash git clone <https://github.com/airbytehq/airbyte.git> cd airbyte ./run-ab-platform.sh
Once you see an Airbyte banner, the UI is ready to go at http://localhost:8000. The default username is 
airbyte
and the password is 
password
. Be sure to change these in your 
.env
file when deploying Airbyte to your servers. Source: [Deploy Airbyte](https://docs.airbyte.com/quickstart/deploy-airbyte)
k
I believe I was able to solve my issue. The "Install and launch Airbyte" section of the GCP install docs contains a curl command to grab certain files from AirbyteHQ. The command as written in the doc was not appropriately curling the docker-compose yaml file. I had split out the command into three separate curl statements for a script I'm writing to automate install of Airbyte upon VM startup. Those commands were old (though only a few weeks old...) and weren't matching up with the command from the docs. I modified my commands (they were pulling from the wrong place) but kept intact three separate curl commands. That has resulted in a successful install.
14 Views
Open in Slack
PreviousNext
Powered by