Hi openBalena Team, I’ve just been notified by GitHub that version 3 is launched with support for newer Balena CLI versions and newer balenaOS versions. Awesome work! I’ll try it out as soon as possible. I just have a couple of questions about the upgrade. Is it as simple as pulling openBalena …

Just another update for people who are interested: I’ve created a fresh openBalena v2 instance once again. Created some devices with balenaOS 2.48.0, deployed some releases, checked if they updated and they did. Next, I backed up all volumes. Destroyed my VPS, created another VPS, applied the backu…

Hey Bart, thanks for the summary, I’m sure it would be helpful to others searching for the same upgrade path. Regarding what you said about the 2.48.0 devices working, is is possible that only a specific path/function had breaking functionality which might end up in unexpected behavior, so we defini…

I’ve finally upgraded my production server to v3.1.1. All worked fine! However, I’ve updated my development Pi using the hostapp-update command and updated the supervisor and pushed my containers to the Pi via balena push <local-ip>, and my volume was lost where some credentials were saved. I’m try…

balena push <local-ip> only works in Local Mode. Are you sure that’s what you’re doing? You’re meant to make a release with balena build/deploy.

Yeah, but this was my development Pi, which has local mode active. I’m using that to test my new code via the balena push <local-ip> command.

Did you turn Local Mode off? All volumes and images on the device are removed when Local Mode is toggled off.

Nope, didn’t turn it off. Is it possible that when the device can’t connect with the openBalena API, it turns local mode off by default or something?

No, I don’t think so. So let me confirm my understanding – this device has always been in Local Mode, you have been pushing code, then updated the host OS, pushed again and found out the volumes wiped? Did you not change anything in the compose file you are pushing in the meantime? If so, that look…

This device was always in Local Mode. I’ve updated the HostOS (from v2.48.0 to v2.60.1), updated the supervisor (from v10.8.0 to v11.14.0) and started pushing code again. My container booted and it checks for a file in the volume, and it said it didn’t exist where it did before. So I checked the vol…

I see. This sounds like a bug with balena push, the new Supervisor or the Supervisor handling Local Mode after a host OS update. We’ll need to dig into this further. Can you please try one more thing? Ensure the device is in Local Mode and the volume exists, then take down the server so the device c…

Upgrading from v2.x.x to v3.x.x

openBalena

gerb0n January 25, 2021, 12:30pm 37

@anujdeshpande I meant HostOS upgrades. I know this topic is 12 months old but this topic also mentions it was not supported at the time.

Topic		Replies	Views
PSA: Host OS Updates & openBalena openBalena psa	30	3774	August 24, 2023
Roadmap for BalenaOS Updates in OpenBalena openBalena	15	3931	January 10, 2025
openBalena 2024 openBalena	9	738	February 28, 2025
openBalena Production ready? openBalena	6	1903	October 3, 2019
Upgrading Custom Host OS with OpenBalena openBalena	17	2012	October 6, 2022

Upgrading from v2.x.x to v3.x.x

Related topics