# RC v7.x to v8.0.1 needing to upgrade MongoDB to v8.2 **URL:** https://forums.rocket.chat/t/rc-v7-x-to-v8-0-1-needing-to-upgrade-mongodb-to-v8-2/22676 **Category:** Upgrade Help **Created:** [January 15, 2026, 8:06am UTC](https://forums.rocket.chat/t/rc-v7-x-to-v8-0-1-needing-to-upgrade-mongodb-to-v8-2/22676 "2026-01-15T08:06:26Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp) #### Post date: [January 15, 2026, 6:56pm UTC](https://forums.rocket.chat/t/rc-v7-x-to-v8-0-1-needing-to-upgrade-mongodb-to-v8-2/22676/3 "2026-01-15T18:56:34Z")
Always search first. > [@Bitnami Image Removal Impacting Older Helm and Docker Compose Deployments](https://forums.rocket.chat/t/bitnami-image-removal-impacting-older-helm-and-docker-compose-deployments/22551): > > Hi everyone, We’d like to inform you about a recent issue affecting some Rocket.Chat self-hosted deployments. Bitnami has removed several of their container images from public repositories (not just deprecated them as we were expecting). This change affects older Helm charts and Docker Compose configurations that reference Bitnami’s MongoDB images. If your environment attempts to pull these images again (for example, during a re-deployment, scaling, or node replacement), you might encounter “… Follow the docs properly and use a .env file > **[Deploy Rocket.Chat with Docker & Compose](https://docs.rocket.chat/v1/docs/deploy-with-docker-docker-compose)** > > Set up Rocket Chat using Docker and Docker Compose. Ensure secure communication, operational resilience, and scalable collaboration on self-hosted servers. And > **[GitHub - RocketChat/rocketchat-compose: Docker / Podman Compose](https://github.com/RocketChat/rocketchat-compose)** > > Docker / Podman Compose --- _[View the full topic](https://forums.rocket.chat/t/rc-v7-x-to-v8-0-1-needing-to-upgrade-mongodb-to-v8-2/22676)._