# Bug - Upgrade from 3.29.1 to 3.30.0

**URL:** https://discussions.eramba.org/t/bug-upgrade-from-3-29-1-to-3-30-0/8773
**Category:** Forum - Installation
**Tags:** docker
**Created:** [May 29, 2026, 6:27pm UTC](https://discussions.eramba.org/t/bug-upgrade-from-3-29-1-to-3-30-0/8773 "2026-05-29T18:27:21Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![ENI-Changelog](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/e/7c8e57/32.png) [@ENI-Changelog](https://discussions.eramba.org/u/ENI-Changelog)
#### Post date: [July 17, 2026, 2:37pm UTC](https://discussions.eramba.org/t/bug-upgrade-from-3-29-1-to-3-30-0/8773/8 "2026-07-17T14:37:03Z")

</div>

AFAIK:

We have faced a similar issue when upgrading eramba to the latest version.

We had to update the repository as in:

> [@Updating the Docker Repository](https://discussions.eramba.org/t/updating-the-docker-repository/7521):
>
> With release 3.27.0, we need to update the versions of the containers (Redis, MySQL) that are pulled when Eramba is built. To do this, we must ensure that the Docker repository is running the latest version. This short guide explains the required steps. Step 1: Stop running containers Before updating, stop the containers. For Community edition: docker compose -f docker-compose.simple-install.yml down For Enterprise edition: docker compose -f docker-compose.simple-install.yml -f docker-comp…

It somehow relies to a repository/url that doesn’t exist anymore.

Unfortunately the engineer who fixed it, is currently not available. Otherwise i would have asked for clear instructions.

---

_[View the full topic](https://discussions.eramba.org/t/bug-upgrade-from-3-29-1-to-3-30-0/8773)._