Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The official Rocketchat docker-compose needs to be updated for newer version of MongoDB #23479

Closed
Taubin opened this issue Oct 17, 2021 · 3 comments · Fixed by #23426
Closed

Comments

@Taubin
Copy link

Taubin commented Oct 17, 2021

Description:

Using the rocketchat docker-compose file here: https://raw.githubusercontent.com/RocketChat/Rocket.Chat/develop/docker-compose.yml the instance installs Mongodb v4.0. When starting up rocketchat, it gives a warning stating mongodb 4.0 has been depreciated and needs to be at least 4.2. Updating the file to just 4.2 breaks due to changes in mongodb's file system. The docker-compose needs to be updated properly.

Steps to reproduce:

  1. Install docker-compose version of rocket chat using the official instructions here: https://docs.rocket.chat/quick-start/installing-and-updating/docker-containers/docker-compose
  2. You will receive an error stating mongodb is depreciated
  3. You will also receive multiple messages on your installation telling you it's depreciated.

Expected behavior:

The version of mongodb to be updating and the documentation updated to reflect the changes/

Actual behavior:

rocket_chat_depreciated

rocket_cat

Server Setup Information:

  • Version of Rocket.Chat Server: 4.0.2
  • Operating System: Ubuntu 20.04
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version: 4.0

Client Setup Information

  • Desktop App or Browser Version: N/A
  • Operating System: N/A

Additional context

@debdutdeb
Copy link
Member

Hi.

I have a PR currently open to update the whole compose file.

#23426
#23425

@WingsLikeEagles
Copy link

This probably isn't any help at all. I'm just sharing for the informational purposes.

I had RocketChat 3.15.0 running in a container with MongoDB 4.0.23 running in a replica set with a couple of containers.
To move to MongoDB 4.2.16, I did:

  • mongodump on MongoDB 4.0.23 containers
  • shutdown all the containers (RocketChat first)
  • started new MongoDB 4.2.16 containers (with empty data volumes, joined them to a replica set)
  • mongorestore to new containers
  • start RocketChat container.

This seemed to successful and running for a couple of weeks now.

@sneakyx
Copy link

sneakyx commented Feb 27, 2022

As far as I understood, the --smallfiles options have to be removed, right?

@kodiakhq kodiakhq bot closed this as completed in #23426 Jun 10, 2022
kodiakhq bot pushed a commit that referenced this issue Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants