Has anybody faced an issue with airbyte-temporal not starting and writing next errors

airbyte-temporal    | + nc -z db 5432
airbyte-temporal    | nc: bad address 'db'
airbyte-temporal    | + '[' 1 -eq 0 ']'
airbyte-temporal    | + echo 'waiting for postgresql to start up'
airbyte-temporal    | + sleep 1
airbyte-temporal    | waiting for postgresql to start up

i have not

is the database container starting up properly?

it depends on the db in the airbyte-db container

hmm, I think that I somehow ran out of disk space….

airbyte-db          | initdb: error: could not create directory "/var/lib/postgresql/data/pg_wal": No space left on device

But thats actually strange because I have ~100gb free

Is that free disk space allocated to Docker? Built images usually take up a ton of space for me personally.

docker rm -f $(docker ps -a -q)
docker volume rm $(docker volume ls -q)
docker image prune  -a
docker system prune

(warning this nukes all docker images and volumes, but this is what i use when i run into this problem)

well usually I do next command

docker rm -f $(docker ps -a -q -f name=airbyte)
 docker volume rm $(docker volume ls -q -f name=airbyte)

everything was working fine, until I decided to switch versions here and there to force server to return Airbyte Version mismatch error. And at some moment db stopped working.

I tried to nuke volumes + all other info ( command above +

docker system prune -a

). It was not helping, but I restart macos, deleted bunch of files and applications and now everything is working…. Thank you all guys for the help 🙂 @charles @Jared Rhizor (Airbyte)

lol. nice.

tbh, when i get in these weird states, restarting docker for mac often fixes things. docker seems to get into a whack state somtimes.