-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded to use newest version of mongo & fixed data volume binds #10
Conversation
mongo's repo location seems to have updated, replaced every instance of dockerfile/mongodb with library/mongo
wide scale replacing of dockerfile/mongodb with library/mongo did not account for the URL change to point at the new mongo location
This line consistently errored out because it would not find the file specified and then the nginx.conf file would not get copied over
This reverts commit 4fc31bf.
BUG KILL- thanks to @patrickmslatteryvt for helping me fix the permission error when mounting local directory to /data/db
must run -v binds to local dirs as --privileged
This reverts commit b0e8f3a.
This reverts commit 27805bd.
This reverts commit 44afcdf.
Awesome work. Looks excellent reviewing on mobile, I'll merge it when I'm back at a legitimate workstation. Great finds all around, really appreciate it. |
Upgraded to use newest version of mongo & fixed data volume binds
@mut3 -- thanks again! Appreciated it. Realized on your profile, you're also in Burlington, VT. Small world, as I am too. You should come drop by LaboratoryB.org and our spot on pine street at some point, I owe you a beer (or tea, if that's how you roll). Thanks Will. |
@dougbtv I was planning to sometime soon. I realized that i didnt update the |
Thanks @mut3 -- went ahead and manually corrected it, good eye. It's in master now, too. |
I noted in #12 issues I believed to be outside the scope of this PR and did not stop the app from running with an attached mongo db. |
bowline was building and relying on the deprecated `dockerfile/mongodb'
https://registry.hub.docker.com/u/deprecateddockerfile/mongodb/
mongo has moved to 'library/mongo' and command syntax has changed somewhat
https://registry.hub.docker.com/_/mongo/
I upgraded the build_it and run_it scripts to use the newer and maintained version of mongo.
Due to an unrelated issue with container permissions I was unable to get the scripts to execute.
On line 30 of
build_it.sh
:docker run -d -v $MONGO_DIR:/data/db --name temp_mongo library/mongo
(port binding to 27017 is now done automagically by mongo)
This container would exit as soon as it was started, meaning the link on line 36:
would fail, because you cannot link to a dead container.
The
temp_mongo
container was crashing and burning due to an error:That chown call comes from line 9 of the
docker_entrypoint.sh
script that is part of the mongo container.https://github.com/docker-library/mongo/blob/master/3.0/docker-entrypoint.sh
The solution for this error, which would kill any
docker run
command with a-v
data volume bind to a local directory, is to have the container run in--privileged
mode, allowing it to access the host file system.https://docs.docker.com/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration
After adding the
--privileged
flag to lines that had previously error'd out inbuild_it.sh
andrun_it.sh
I successfully* ran a locally hosted Bowline on my CentOS 7 box with Docker 1.6.0.