From 6bd1f5a3a70b00d69806314812376257980ed0b4 Mon Sep 17 00:00:00 2001
From: Pradeep Kilambi <pkilambi@cisco.com>
Date: Tue, 25 Nov 2014 17:23:08 -0500
Subject: [PATCH] Fix to not fork mongod so mongodb container works as expected

For some reason forking the mongod process seems to cause issues
when the container comes up. If i remove this and run the
images with detach and publishall flags i can connect to
mongo instance.

Change-Id: I0b7193e6369084e3aeec857607dda9c3f235770d
---
 docker/mongodb/Dockerfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker/mongodb/Dockerfile b/docker/mongodb/Dockerfile
index 2f74a46d7e..438a2919c9 100644
--- a/docker/mongodb/Dockerfile
+++ b/docker/mongodb/Dockerfile
@@ -10,4 +10,4 @@ VOLUME /var/log/mongodb
 
 EXPOSE 27017
 
-ENTRYPOINT exec /bin/mongod --dbpath /data/db --fork --logpath /var/log/mongodb/mongo.log --noprealloc --smallfiles
+ENTRYPOINT exec /bin/mongod --dbpath /data/db --logpath /var/log/mongodb/mongo.log --noprealloc --smallfiles