Mongo connection errors and cannot log in about learninglocker2-docker HOT 4 CLOSED

@uglycoyote, thank you for trying this.

I think that what depends_on does is to ensure that a dependency container, i.e. mongo, starts before the other one. However, the mongo application needs some more time to start after the container launches, especially for the first time. I'm not sure it is possible to express such wait times in docker-compose.

In your setup, could you please try the following:

1. docker-compose down
2. Clear the $DATA_LOCATION directory
3. docker-compose up -d mongo and then observe docker-compose logs -f mongo, and wait until it gets ready
4. docker-compose up -d to bring up all the other services

If it works for you, we can probably add it to my README file as suggested steps for the first launch of the whole application.

from learninglocker2-docker.

Yes, that works, so might be good to add to the readme.

from learninglocker2-docker.

(thanks very much!)

from learninglocker2-docker.

Done: b76b8e5. Thanks!

from learninglocker2-docker.