I did some further digging in the azure documentation:
So when you stop your container group it recycles everything - so the container state is not preserved.
So if flows are stored in the writable container layer they are all lost.
When restarting a container it will pull a new image if the container image is updated which most likely is the case as recently a new node-red image version is available on docker hub.
So this new image, will complete replace the old image including the writable container layer containing the flows you have stored there.
To overcome this you must assure that the flows are not stored in the writable container layer but outside the container in a volume.
So for this you need to
- create an Azure file share:
Mount Azure Files volume to container group - Azure Container Instances | Microsoft Learn - mount the Azure file share as a volume in the container with mount path
/data
