MongoDB unable to start due to incorrect option being passed

[kylehodgetts]

When following the instructions in the README, I've found that the API pods enter CrashLoopBackoff due to being unable to connect to the MongoDB instance.

When checking the logs of the mongopod, I find the following:

...
INFO  ==> Starting mongodb...
INFO  ==> Starting mongod...
Expected boolean switch but found string:  for option: net.ipv6
try '/opt/bitnami/mongodb/bin/mongod --help' for more information

When trying to start mongod, as you can see, a string parameter is passed where a boolean one should be.

May also be the case for #487

[relenteny]

+1 Just saw the same issue.

[michaelgriffiths-mclaren]

+1, I'm using chart version 0.6.4

[relenteny]

Got around it by specifying the previous MongoDB image in the values yaml file I use when starting Monocular:

mongodb:
   image:
      tag: 3.6.6-debian-9-r36

So far, looks to be working fine.

[kylehodgetts]

This worked. I'm going to leave the issue open until it's resolved though