Hello! I installed Airbyte according to Deploying Airbyte on GCP instructions. I'm on a private VPC within Google Compute Engine. Everything went OK up until:

# In your ssh session on the instance terminal
mkdir airbyte && cd airbyte
wget <https://raw.githubusercontent.com/airbytehq/airbyte/master/{.env,docker-compose.yaml}>
docker-compose up -d

Here's the error:

user:~/airbyte$ docker-compose up -d
ERROR: Couldn't connect to Docker daemon at <http+docker://localhost> - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

Any ideas?

It looks like docker isn’t running on the GCE instance

Ah! Just solved this but leaving it up in case others have this issue - ran the command:

sudo usermod -aG docker $USER

and logged back out/back in.

Thanks for the reply @Jared Rhizor (Airbyte) - that was my first thought too, but I checked the status and it was running

Oh interesting, I think this is the first case we’ve encountered of a permissions issue showing that kind of error.

strange! If there're any other printouts you'd like to see on this let me know, glad to help.

From this github issue it looks like that error can occur when the docker.sock file isn’t accessible by the current user, which is why it’s fixable by adding the user to the docker group and logging in again.

Interesting it manifested this way. I’ll add it to our FAQ. We only address the non-running daemon problem atm.