Open Debapriya-Tula opened 5 years ago
What's your docker-compose version?
1.8.0 build 94f7016.
As was asked to.
On Sun, Feb 3, 2019, 2:16 PM Pigeon notifications@github.com wrote:
What's your docker-compose version?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Cloud-CV/Fabrik/issues/510#issuecomment-460033810, or mute the thread https://github.com/notifications/unsubscribe-auth/AhiMzhEC9dw25Y1Tt_sikvhWCNZhebbqks5vJqH8gaJpZM4aUt_B .
Can your docker-compose run other docker-compose.yml?
It was able to run other .yml files. I tried installing docker-compose again. It did not pose the same error this time. But now I am facing a new error while running docker-compose up as was mentioned in the steps.
Starting fabrik_db_1 ... error
908faf63e45b8e07e6871e2724ab097183e4d5dbfbafa): Error starting userland proxy: listen tcp 0.0.0.0:6379: bind: address already in use
Recreating reactjs ... done
ERROR: for fabrik_db_1 Cannot start service db: driver failed programming external connectivity on endpoint fabrik_db_1 (db2f8deb65ea53cb7f9396cb8a5adf3a1cce3630ea81d6316f7f8094dd0ab8c9): Error starting userland proxy: listen tcp 0.0.0.0:5432: bind: address already in use
ERROR: for redis Cannot start service redis: driver failed programming external connectivity on endpoint fabrik_redis_1 (7012507ad4faefe9d4f908faf63e45b8e07e6871e2724ab097183e4d5dbfbafa): Error starting userland proxy: listen tcp 0.0.0.0:6379: bind: address already in use
ERROR: for db Cannot start service db: driver failed programming external connectivity on endpoint fabrik_db_1 (db2f8deb65ea53cb7f9396cb8a5adf3a1cce3630ea81d6316f7f8094dd0ab8c9): Error starting userland proxy: listen tcp 0.0.0.0:5432: bind: address already in use
ERROR: Encountered errors while bringing up the project.
Sorry for closing the issue mistakenly.
@Debapriya-Tula , looks like you have been running some other docker/ docker-compose command which is already using the ports (maybe cloudcv/EvalAI ? ). In my case I had been building both cloudcv/EvalAI and cloudcv/Fabrik simultaneously which led to the same error.
Stop other running docker containers and/ or docker-compose commands. That should fix it.
Another way would be to run "docker ps" and see which of the ports are already occupied by which containers and stop them by doing "docker container stop
the expected behaviour Command should have run with no errors
the observed behaviour Throws DistributionNotFound error
Traceback: