Hi @banto-78 ,
I think there’s some confusion here. It does indeed sound like data is not being persisted across host OS flashing.
To clarify, any balenaOS version downloaded for an application will run the docker services associated with that application.
The balenaCloud service allows you to create an application, which consists of one of more docker services which are run on a device. Any device provisioned against the application will therefore download and run the docker services associated with it. This allows customers to carry out fleet management by provisioning devices with the same image, knowing that each device will run the application associated with it.
What you’re seeing is exactly what should occur. Regardless of the version of the host OS, the same application will run on any device provisioned with a device image assocated with the application being used to download the image. If you need devices to run different services, then a new application should be created with the different services required and devices provisioned with images associated with that new application.
balenaOS versions do not alter a version of an application, they are different versions of the Operating System that a device runs, where later versions of balenaOS include the latest features/bugfixes for the OS, they don’t version the application.
If you want to run different release versions of a single application, you can use staged versioning (release pinning), documented here: https://github.com/balena-io-projects/staged-releases
Hopefully this clears up any confusion! Please let us know if you have any other questions.
Best regards, Heds