Closed rasdani closed 1 year ago
Hi rasdani,
this looks like the database container (PG_CONTAINER -> graphql-postgres) couldn't be found on startup.
When you run ./start
after the error shows, could you enter docker ps
in a console and provide the results so we can try to determine if there might be a naming issue?
docker ps
shows no containers even with sudo
and -a
(since I deleted all trying to troubleshoot).
I tried deleting and cloning the repo again, same issue on ./start
.
Will try pip install
next.
EDIT: same error with pip install
and refinery start
EDIT2: docker is pulling images again, after running Docker Desktop beforehand, fingers crossed! But didn't run Docker Desktop the first time I got refinery working. :man_shrugging:
Not having any container would explain the error :D Doesn't explain the missing containers so that's a bit harder to work with. Since alfred (our startup manager container) is pulled and does some things I don't think there is an issue with containers in general.
One message in your proved logs shows:
could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network
Nothing I've seen before but looking around a bit it might be related to a VPN issue. Are you using a VPN? Stackoverflow Link Github Issue link
My VPN was indeed the culprit! Works likes a charm now :partying_face: Somehow I found only suggestions to clear network/delete containers, anyway thank you! :pray: :relieved:
Awesome & Happy to help 🙂
Describe the bug I managed to
./start
and./stop
once and refinery worked well. On second startup./start
throws:To Reproduce Steps to reproduce the behavior:
./start
Expected behavior Docker should boot up with already fetched image/dependencies.
Desktop (please complete the following information):
Additional context Starting from cloned git repo. I already tried
docker network prune
and evendocker container prune
.