![]() Now create a database dump of your existing MongoDB: docker-compose up -dĭocker-compose exec mongo mongodump -archive=/dump/mmap -gzipĬp. Mv docker-compose.yml /opt/rocketchat/docker-compose.ymlĬheck your docker-compose.yml and make sure that you have an existing volume for the dump folder defined:Īlso make sure that the. To prepare for the upgrade: docker-compose down Initially, my RocketChat was installed in a /docker/rocketchat folder and so this did not work. To begin with, your docker-compose.yml file MUST be located in the /opt/rocketchat folder before this can work. ![]() I have tried this procedure several times and failed before I discovered the solution. Before MongoDB can be upgraded to the next version which is MongoDB v4.2, you must change the MongoDB database engine in Mongo v4.0.x from the mmap engine to the wiredTiger database engine. Mongo v4.0.28 uses the mmap database engine. The upgrade of MongoDB is a multi-step process. If you are running RocketChat v4.x with MongoDB v4.0, you are seeing a message from the RocketChat bot indicating that Mongo v4.0.28 is deprecated and should be upgraded. Beginning in RocketChat 5.0, There is a requirement to be running at least MongoDB v4.2. This will upgrade RocketChat to any 4.x version. Once you have updated the version: docker pull rocketchat/rocket.chat:latest RocketChat can be easily upgraded by updating the “RocketChat” container version in your docker-compose.yml file. Here’s the login prompt you’ll see to log into is a guide to upgrading RocketChat deployed in Docker. You should configure SMTP immediately for cases where a user can’t log into Rocket.Chat (Administration > Email > SMTP).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |