You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a race condition I haven't figured out yet.
Just keep running the docker-compose up command over and over until it starts.
You can check if it is running using the docker ps command.
You should see all three containers when things are working correctly:
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ab4ac0d3bc46 bgpdash_flask "/usr/bin/supervisord" 22 seconds ago Up 18 seconds 0.0.0.0:80->80/tcp bgpdash_flask_1
ec2546ce400b bgpdash_gobgp "/bin/sh -c /root/gob" 22 seconds ago Up 6 seconds 0.0.0.0:179->179/tcp bgpdash_gobgp_1
e520b32708a4 bgpdash_mongo "/entrypoint.sh mongo" 24 seconds ago Up 22 seconds 27017/tcp bgpdash_mongo_1
The text was updated successfully, but these errors were encountered:
However the container isn't peering, I see a BGP OPEN message from my router followed by an ACK & FIN from my MacBook. This tells me that the router is attempting to peer and either my Mac or the goBGP container is closing the connection.
When starting the docker images with either:
The gobgp image doesn't stay running.
There is a race condition I haven't figured out yet.
Just keep running the docker-compose up command over and over until it starts.
You can check if it is running using the docker ps command.
You should see all three containers when things are working correctly:
The text was updated successfully, but these errors were encountered: