Upgrade from buster to bullseye to bookworm broke 80% of umbrel (but not 100% 🤔)

[diyoyo]

Hi, I was so happy to learn that Debian 12 was solving the nightmare of system python versions etc that I wanted to upgrade. Yet, I did it sequentially from buster to bullseye to bookworm, and it started breaking already in bullseye. Basically, I had to install the proper "docker compose" (and not "docker-compose") and then look for all the scripts where umbrel still used "docker-compose" as a command. Then only, umbrel started working under Debian 12...

except... only Bitcoin and Lightning node are starting correctly. All other apps are under "Starting..." status forever (in the Web UI), and basically, docker logs state that the app_proxy cannot find the server for each app. My three hypotheses are:

• it's a network problem (maybe I docker pruned by mistake)
• a signature change during the upgrade
• a folder permission problem (but which folder?)

I don't know where to start to fix this. I always perform scripts actions directly from umbrel's folder.

I also don't understand why Bitcoin is working and not the others?

Thanks for your help.

[diyoyo]

Oh, I have a new hypothesis: I should also replace "_" by "-" in addresses when containers are looking for other services in the same stack. Or even completely remove the prefixes, ie replace "element_web_1" by just "web" in the docker-compose.yml relationships. I'll keep you posted.

[diyoyo]

Yes, replacing the "_" with "-" worked! Actually, removing the entire prefix was a good idea, but did not work here because the dependency is actually declared through en environment variable, rather than "properly" using stack's yaml nomenclature.

So to summarize, maybe that's a risk you don't want to take (and I decline any responsibility if you have problems) but in case you want to upgrade from buster to bookworm, the following might help :

• it has not ruined my wallet

• there was not data loss is volume bindings, as far as I can tell on my instance

  • you need to remove docker-compose and install a clean version of compose, as explained here : https://docs.docker.com/engine/install/debian/

• you need to look for all occurrences of docker-compose in the umbrel's root dit, BUT be careful:

  • only replace those that are actual commands from docker-compose to docker compose

    • make sure that you don't replace strings that are referring to yaml files docker-compose.yml

• in the app-data folder, you need to edit all docker-compose.yml (when umbrel is stopped), and replace "_" by "-" in the environment variables that help containers talk to each other in the same stack:

  • For instance: below is the correct string: heimdall-server-1, because once created, the service called server in the heimdall stack will be renamed heimdall-server-1 in the latest versions of docker compose.

    

I hope it'll help someone save time. (I also hope that all this was not supposed to be obvious, but anyway, I learnt some stuff :D )

IMPORTANT EDIT there is one issue though: you have to modify the docker-compose.yml every time you install a new app :(