Closed jdylan closed 6 months ago
I see the same issue — following this README.md with this compose file doesn't work out of the box because the networking is not set up right. @jdylan workaround is good as far as it goes.
You can correct this by replacing database_host = '127.0.0.1'
to database_host = 'mongo'
in the beacon2-ri-api/deploy/conf.py
file. I guess the network interfacing does not really happen via the local host. Your docker setup might be using a different private network configuration.
Anyway, this is how I resolved this issue.
Expected Behavior
When following the instructions in the README the beacon container should be able to access the mongo container with dummy data.
Current Behavior
The beacon server times out, because it cannot establish a connection to the mongo db - below from the logs:
Possible Solution
This is possibly because the containers are on separate networks, the network allocation for each service has been commented out. I managed to get this to work by adding 'network_mode: host' to the docker-compose.yaml, though this has other implications.
Steps to Reproduce
Follow the deployment instructions exactly.
Context (Environment)
Deploying a Beacon V2 instance on an Ubuntu 20.04 VM under openstack.