Replies: 1 comment 2 replies
-
MongoDB container logs. NOTE: how long it takes for the DB to self-initialise (> 3 minutes).
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem
When trying to re-initialise MongoDB (IE: perform a clean wipe), it seems that the
docker-entrypoint.sh
is failing to detect a 'uninitialised' instance of Mongo.Some times when I execute the following steps I do see the following message within the
mongo
container logs.Other times, it does not print the message above and therefore does not initialise.
Steps to reproduce
Steps to run
Reference: docker-compose.yml
Other info
My Docker volumes are NFS mounted volumes running in AWS EFS. When the MongoDB container starts and does not initialise - I see my EFS volume throughput spike and become pinned at 100% until I kill the now-stuck MongoDB container.
Image tag:
mongo:5.0.8
Docker version:
v25.0.1
Docker Compose version:
v2.24.2
docker inspect mongodb-data
Beta Was this translation helpful? Give feedback.
All reactions