11/30/2023 0 Comments Rocketchat upgrade![]() Try to find out what is the safe upgrade path from RC 3.18.3 to RC 4.1.2.Is the move from 3.x to 3.y considered a major or minor update? Or is major version always the first number? Steps to reproduce: ![]() In addition to answering to above question, the terminology of major and minor updates should be clearly visible. Otherwise the functionality may break in unexpected ways.įor example now when we'd like to move from 3.18.3 to 4.1.2, can 4.0.6 be skipped safely? Since different versions include changes to database schema, it is important that one does not skip too many versions of RC when upgrading from LTS versions to the latest available version. Https:///getting-support#rocket.chat-versions contains the latest and supported versions.īut so far we haven't been able to find any official word on the minor versions of RC that can be safely skipped at. Now that you are connected to the container: mongoĭb.adminCommand( )\" &Įcho \"Could not reach MongoDB. You may need to explicitly specify the name by first doing a “docker ps” to see what it is called: docker exec -it mongo bash We now have to change the replication feature set in the database. Once this is completed, perform the following: docker-compose stop mongo The upgrade path is:Įdit your docker-compose.yml and replace the 4.0 with 4.2 in the mongo section and in the mongo-init-replica section. Unfortunately, we cannot upgrade from 4.0 to 5.0 directly. The latest version of MongoDB is 5.0.x to support RocketChat. It should say "MongoDB 4.0.x / wiredTiger (oplog Enabled)Ĭongratulations, you are now using the required wiredTiger database engine with Mongo 4.0.x which is a prerequisite before moving to MongoDB 4.2. Go to the admin – info section and look at the database section. Once this completes, your RocketChat should be up. This may take five minutes or more to complete in the background. Now build the migrator image: docker-compose up -build -d Review the new docker-compose in case you had any customizations that you need to include. You should leave this docker-compose file in place after the upgrade because it is built to support future migrations as well: cp /opt/rocketchat-migration/docker-compose.yml /opt/rocketchat/docker-compose.yml Stop your existing RocketChat: docker-compose stopĭownload the repository for the database engine remapping tool: git clone /opt/rocketchat-migrationĬopy the docker folder that has the dockerfile for the migrator image into your existing compose folder: cp -r /opt/rocketchat-migration/docker /opt/rocketchat/dockerīackup and rename your existing docker-compose.yml file: mv /opt/rocketchat/docker-compose.yml /opt/rocketchat/Ĭopy the new docker-compose.yml file into your compose folder. 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. This is a guide to upgrading RocketChat deployed in Docker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |