-
Notifications
You must be signed in to change notification settings - Fork 649
Cannot start with SSL #165
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
Comments
I am also facing a similar issue. I am experimenting with mongod in docker swarm. When I deploy mongo services in swarm with a The error is - This error occurs only when deploying mongod as a service in the docker swarm. If I start mongod container from an image pulled from docker hub with the exact same configurations as in the service, it works fine. I am not able to figure out the reason. I have tried Changing the port of mongod in docker service. Changing port gives a different error. starting mongod with configurations from command line with starting mongod with configurations from a configuration file mounted inside the mongod container. starting mongod with a configuration My configuration file looks like this -
|
I am also facing the same issue
Dockerfile
Error Logs
|
We added a fix in #167 to account for this; can you pull and see if the latest image works for you? @kkdevenda and @thisismsreddy, unfortunately we don't yet have a good way to have the |
Hey @yosifkit It seems new Image fix this issue,It,s working fine for me , I've also tested with swarm service it's looking good. |
Indeed, this was fixed about as good as it can be without parsing config files in #167. 👍 Thanks for confirming, @thisismsreddy ❤️ |
If I start mongod with ssl enabled, docker-entrypoint.sh will always fail.
on line 106 of docker-entrypoint.sh: if "${mongo[@]}" 'admin' --eval 'quit(0)' &> /dev/null; then
ssl options should be added to the mongo command if the server is started with ssl
e.g. add --ssl --sslAllowInvalidCertificates
if "${mongo[@]}" --ssl --sslAllowInvalidCertificates 'admin' --eval 'quit(0)' &> /dev/null; then
image mongo:3.4
The text was updated successfully, but these errors were encountered: