So I am curious about something,
I have a Pi3B+ in an argonone case, (the one with the fans), it currently is running OctoPi and a custom code-server setup. with a 4gb sdcard that came with my 3d printer
but I noticed that when you push a service update, even if you just modified one service, it rebuilds and redownloads all services. which pushes my storage consumption to 2.8gb by the time it is done updating the services, and then it removes the previous version of the services,
So is there a way for a single service to be updated without rebuilding/downloading all services. For example potentially through the use of diff tools to see which service was modified compared to the previous docker-compose.yml file
Hi,
For devices with storage limitations, we offer the delete-then-download release strategy: Fleet update strategy - Balena Documentation. Although from what I understand of your post, you don’t necessarily want images to be deleted before updating to a new release.
Between two releases where only one service has changed, images should not be redownloaded for services that have not changed. You can verify this by running balena images before and after an update, and comparing the image IDs listed. However, containers will be rebuilt and this is by design, as env vars for containers cannot be changed at runtime, and the Supervisor needs to update container env vars to point to the correct new release so it can manage containers accurately.
If you’re unsure when looking at the output of balena images pre and post-update, please paste the output here and we can take a look together. Thanks, and hope this helps!
Regards,
Christina
Also, do you have deltas enabled, and what is the size of your delta update? You can see this kind of info by looking at the output of balena images as well.