transfer data from a dumpfile to a new instance of rocket chat
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, mongodb
- Domain
- databases, infrastructure
Research direction
Start with the docker-compose configuration, the db.dump file, and the mongodump/mongorestore commands described in the issue; compare the new container setup with the Rocket.Chat 5.2.0 source instance and inspect the startup logs. Done means the restored instance shows the previous users, rooms, channels, and custom CSS instead of the default setup wizard.
Written by the indexing model from the issue text.
Description
Hello, I have a rocket chat server (v 5.2.0) running on docker container and then backed up data using: docker exec db sh -c "mongodump --archive" > db.dump
I created a docker-compose file, that runs a new instance of rocket chat and MongoDB, then restored the dump file using: docker exec -i db sh -c "mongorestore --archive" < db.dump.
After the docker-compose startup, even when the logs show data transfer was successful, I'm always redirected to the default setup wizard, I looked into it and found i needed to add OVERWRITE_SETTING_Show_Setup_Wizard=completed in the environment, but even then, no data is displayed, it just asks me to log in, the credentials were wrong and I had to create a new user, and even then it's the default rocket chat interface with none of my rooms, channels, custom css...
How can add the data from a dumpfile of a previous rocketchat server to this new one running using docker-compose?
Thanks
- Dominant language
- Dockerfile
- Stars
- 336
- Forks
- 226
- Avg merge
- 21d 4h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/Docker.Official.Image
-
Difficulty 4/5 1-2 days Newbie friendliness 25/100
RocketChat/Docker.Official.Image#302 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
RocketChat/Docker.Official.Image#290 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
RocketChat/Docker.Official.Image#267 · 1 comment · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
RocketChat/Docker.Official.Image#248 · 7 comments · 6 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in RocketChat/Docker.Official.Image
Similar issues
-
ctx_doctor opencode: D5 hook round trip FAIL — linkSync EACCES on Android/f2fs (hard links denied)Openbug fixed-on-main repro-ready
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mksglu/context-mode#1385 · 2 comments ·
-
bug P3-low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
audit/cpu-2026-11 complexity/S confidence/confirmed durability performance server severity/high
Difficulty 1/5 Under an hour Newbie friendliness 85/100
prime-radiant-inc/evener#6414 ·
Maintainers usually reply within 1 day
-
request-theme
Difficulty 2/5 Under an hour Newbie friendliness 62/100
LizardByte/ThemerrDB#10024 · 2 comments ·