Closed BrookeDot closed 2 years ago
My package.json
does show "mongoose": "^5.11.12",
Can you show you docker-compose.yml? What version do you use there for mongo?
Can you show you docker-compose.yml? What version do you use there for mongo?
It doesn't seem to have a Mongo version there. It's the stock file from the repo. Is that part of the problem?
$ more docker-compose.yml
version: "2"
services:
ackee:
image: electerious/ackee
container_name: ackee
restart: always
ports:
- "3000:3000"
environment:
- WAIT_HOSTS=mongo:27017
- ACKEE_MONGODB=mongodb://mongo:27017/ackee
env_file:
- .env
depends_on:
- mongo
mongo:
image: mongo
container_name: mongo
restart: always
volumes:
- ./data:/data/db
Have an Ackee instance running an older version of Ackee and try to upgrade. Run docker-composer pull && docker-compose up and you'll see MongoDB failures and Ackee fail to start.
Hm, that what I'm doing, too. Docker should pull the latest image for both ackee and mongo when running docker-composer pull && docker-compose up
.
Closing this, deleting the GitHub codebase then doing a clean checkout "fixed" it. Have no idea what was going on but here we are :D
π Describe the bug
I'm not sure how this happens, but my current MongoDB version is 4.4.6 with Ackee 3.1.1. Whenever I try to upgrade the images using docker-composer Mongo throws a few errors.
It looks like at some point MongoDB was updated to v5 and now v6. It would be great to have documentation on how to upgrade Ackee that includes how to upgrade MongoDB
π To Reproduce
Have an Ackee instance running an older version of Ackee and try to upgrade. Run
docker-composer pull && docker-compose up
and you'll see MongoDB failures and Ackee fail to start.π‘ Expected behavior
I would expect Mongo DB to be updated and all code just to work.
βοΈ Environment