Below are the steps that leads to the issue and what I had tried to solve it.
After installing docker and docker-compose, running docker-compose run app ./lbrytv db_migrate_up will at first encounter the error lbry/odysee-api:latest-dev not found, fix it by changing the image tag to lbry/odysee-api:latest
After changing the image tag, all images are pulled successfully but docker-compose error out with panic: dial tcp 127.0.0.1:5432: connect: connection refused. Full log are as shown in the section below.
I am not familiar with postgres so I perform some online searches and most of the results indicate that I should specify the ip address of the postgres docker container instead of localhost.
Search this repo and decided to trial and error by modify odysee-api/sqlboiler.toml and odysee-api/sqlboiler.toml to use the docker 172.x.x.x address.
The log still indicates that it is trying to use localhost, did more search and found the database connection config is acquired in odysee-api/main.go from github.com/lbryio/lbrytv/apps/lbrytv/config
I am not familiar with both postgres and Go so I am facing difficulty in moving forward. Any pointers for me to debug further or does this looks like an actual issue?
We generally don't run off the docker image locally so the process is a bit out of sync, thanks for bringing this to my attention. Should be fixed now, just git pull and docker-compose up app is enough.
Description
Below are the steps that leads to the issue and what I had tried to solve it.
docker-compose run app ./lbrytv db_migrate_up
will at first encounter the errorlbry/odysee-api:latest-dev
not found, fix it by changing the image tag tolbry/odysee-api:latest
panic: dial tcp 127.0.0.1:5432: connect: connection refused
. Full log are as shown in the section below.localhost
.odysee-api/sqlboiler.toml
andodysee-api/sqlboiler.toml
to use the docker 172.x.x.x address.odysee-api/main.go
fromgithub.com/lbryio/lbrytv/apps/lbrytv/config
I am not familiar with both postgres and Go so I am facing difficulty in moving forward. Any pointers for me to debug further or does this looks like an actual issue?
System Info
Full Log