Description
This is a fresh install of Debian and I am trying to setup Rocket.Chat following this guide: Deploy Rocket.Chat with Docker & Compose
The container named “rocketchat-compose-mongodb-1” keeps restarting over and over complaining about file ownership. Also the container name “rocketchat-compose-mongodb-init-container-1” can’t seem to connect to itself? It seems strange that following the guide to the letter would have so many issues.
Server Setup Information
- Version of Rocket.Chat Server: 8.0.1
- Operating System: Debian 13
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: NA
- NodeJS Version: NA
- MongoDB Version: mongodb-community-server:8.2-ubi8
- Proxy: NA
- Firewalls involved: NA
Any additional Information
ds-rocket-01:~/rocketchat-compose$ docker logs rocketchat-compose-mongodb-1
=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) …
=====> /data/db ownership OK (1001) - starting MongoDB
=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) …
=====> /data/db ownership OK (1001) - starting MongoDB
=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) …
=====> /data/db ownership OK (1001) - starting MongoDB
=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) …
ds-rocket-01:~/rocketchat-compose$ docker logs rocketchat-compose-mongodb-init-container-1
- echo ‘=====> Waiting for MongoDB to be healthy before initiating replica set…’
- mongosh ‘mongodb://mongodb:27017/?directConnection=true’ --eval ‘db.adminCommand(“ping”)’
=====> Waiting for MongoDB to be healthy before initiating replica set… - echo ‘=====> MongoDB not ready yet, retrying in 5 seconds…’
- sleep 5
=====> MongoDB not ready yet, retrying in 5 seconds… - mongosh ‘mongodb://mongodb:27017/?directConnection=true’ --eval ‘db.adminCommand(“ping”)’
=====> MongoDB not ready yet, retrying in 5 seconds… - echo ‘=====> MongoDB not ready yet, retrying in 5 seconds…’
- sleep 5