Hello I ve followed the steps in the documentation <https do Airbyte #ask-ai

Hello, I've followed the steps in the documentatio...

Riley Griffith

05/03/2023, 1:53 PM

Hello, I've followed the steps in the documentation https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine/ but for some reason am unable to get the local db setup working upon running

docker compose up -d

Copy code

password authentication failed for user "docker"

and

Copy code

Role "docker" does not exist.

This is especially strange because I have gotten the same exact setup working in another vm instance, I have verified that there are no differences between

flags.yml

docker-compose.yaml

, and

.env

in the two instances, yet it is still failing on one. Any suggestions? In the failing instance, I did have to take extra steps to allow

docker compose up -d

to be run without sudo, whereas I did not have to do this in the first so that could be a clue as to what is going wrong.

kapa.ai

05/03/2023, 1:53 PM

A message from kapa.ai

kapa.ai

05/03/2023, 1:53 PM

Hmm, I don't know enough to give you a confident answer yet. However, I can suggest some general troubleshooting steps based on the information extracts. 1. Ensure that all Airbyte containers are running by executing

docker ps

. You should see 4 containers running. If not, try the following steps: -

docker compose down -v

docker compose up

Keep in mind that these commands will delete all containers, volumes, and data created by Airbyte. We do not recommend this if you already have connections created. 2. Check the server logs for any errors by running

docker logs airbyte-server | grep ERROR

. If this command returns any output, run

docker logs airbyte-server > airbyte-server.log

. If these steps don't help, I recommend referring to the [Airbyte Troubleshooting documentation](https://docs.airbyte.com/troubleshooting/on-deploying) for more guidance.

Riley Griffith

05/03/2023, 5:31 PM

If anyone in the future runs into this, I solved this by adding a -v flag to

docker compose down -v

command when restarting the docker compose

Rex Wang

07/19/2023, 4:32 PM

If anyone in the future runs into this, I solved this by adding a -v flag to
docker compose down -v
command when restarting the docker compose

I'm from the future and appreciate your helpful message which saved my poor 2 hours!!

Open in Slack

Previous Next