Problems with Mongo 3.4 image with some requests

Just a heads up for people having issues suddenly with Mongo db. My deploy was crashing the past few days and I think I’ve just figured out why.

Mup uses the mongo:latest image in docker. The image has just been updated in the Docker repo to use the latest 3.4 version of Mongo DB, which has some backward incompatible changes. https://docs.mongodb.com/master/release-notes/3.4-compatibility/#backwards-incompatible-features

In my case $geoNear queries where failling.

I manually changed the mongo-start.sh to lock it to mongo 3.2.11 and everything went back to working.

Here it is the new content of mongo-start.sh

#!/bin/bash

set -e
# we use this data directory for the backward compatibility
# older mup uses mongodb from apt-get and they used this data directory
sudo mkdir -p /var/lib/mongodb

sudo docker pull mongo:3.2.11
set +e
sudo docker rm -f mongodb
set -e

sudo docker run \
  -d \
  --restart=always \
  --publish=127.0.0.1:27017:27017 \
  --volume=/var/lib/mongodb:/data/db \
  --volume=/opt/mongodb/mongodb.conf:/mongodb.conf \
  --name=mongodb \
  mongo:3.2.11 mongod -f /mongodb.conf

[shadowcodex]

This needs to be added as a config option in mup.js

[bensventures]

great news @nosleepfilipe thanks for taking the time to update us 😃

Happy new years too.