# Update Strategy with Single Device **URL:** \ **Category:** Product support\ **Created:** [April 19, 2022, 4:29pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886 "2022-04-19T16:29:22Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [April 19, 2022, 4:29pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/1 "2022-04-19T16:29:22Z")
We are using Raspberry Pi Zero 2’s and have been having some issues with release downloads timing out and restarting. I have seen that the general first step is to switch to “kill-then-download” from [Fleet update strategy - Balena Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/) . I have set that strategy but when I go to one device and move the pinned release, I don’t see anything in the logs about the container stopping before the download and during the download I see the service status as “Running” in the dashboard. Does the update strategy only apply when the fleet-wide pinned release is changed? Thanks Here is an excerpt from the logs of an example device. I went to this device, stopped the service from the dashboard and then changed the pinned release of just that device a minute later. If the device were honoring the “kill-then-delete” strategy, I would expect to see the `Service is already stopped...` message (12:16:42) before the `Downloading delta...` message (12:11:02). ```auto 19.04.22 12:06:45 (-0400) Supervisor starting 19.04.22 12:10:29 (-0400) Killing service 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:10:41 (-0400) Killed service 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:10:41 (-0400) Service exited 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:11:02 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/ae176de89a210ac5d6a3ee6410ee764e@sha256:e3e2266c2e60d95fd4aa678265796a5966f0de520ddca5a0babe2171df05e842' 19.04.22 12:11:58 (-0400) Delta still processing remotely. Will retry... 19.04.22 12:11:58 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/ae176de89a210ac5d6a3ee6410ee764e@sha256:e3e2266c2e60d95fd4aa678265796a5966f0de520ddca5a0babe2171df05e842' 19.04.22 12:12:54 (-0400) Delta still processing remotely. Will retry... 19.04.22 12:12:54 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/ae176de89a210ac5d6a3ee6410ee764e@sha256:e3e2266c2e60d95fd4aa678265796a5966f0de520ddca5a0babe2171df05e842' 19.04.22 12:13:50 (-0400) Delta still processing remotely. Will retry... 19.04.22 12:13:50 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/ae176de89a210ac5d6a3ee6410ee764e@sha256:e3e2266c2e60d95fd4aa678265796a5966f0de520ddca5a0babe2171df05e842' 19.04.22 12:16:41 (-0400) Downloaded image 'registry2.balena-cloud.com/v2/ae176de89a210ac5d6a3ee6410ee764e@sha256:e3e2266c2e60d95fd4aa678265796a5966f0de520ddca5a0babe2171df05e842' 19.04.22 12:16:41 (-0400) Killing service 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:16:42 (-0400) Service is already stopped, removing container 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:16:42 (-0400) Killed service 'api sha256:0b6c4dedcea8e4c3bea911f788545713e5041f9455ab66bac1fea1352d8b800b' 19.04.22 12:16:43 (-0400) Deleting image 'registry2.balena-cloud.com/v2/24e893a57dedff020bc9703403a326b5@sha256:be3721a5e91e3b398961a74b455f08acf79bf49e022cc42e4a55bf602dcf79b3' 19.04.22 12:16:51 (-0400) Deleted image 'registry2.balena-cloud.com/v2/24e893a57dedff020bc9703403a326b5@sha256:be3721a5e91e3b398961a74b455f08acf79bf49e022cc42e4a55bf602dcf79b3' 19.04.22 12:16:52 (-0400) Installing service 'api sha256:3a7cfdf9acc4452a3a50211e5b1b4cdda7a017d6e7501ed11896f23d82c49aa2' 19.04.22 12:16:53 (-0400) Installed service 'api sha256:3a7cfdf9acc4452a3a50211e5b1b4cdda7a017d6e7501ed11896f23d82c49aa2' 19.04.22 12:16:53 (-0400) Starting service 'api sha256:3a7cfdf9acc4452a3a50211e5b1b4cdda7a017d6e7501ed11896f23d82c49aa2' 19.04.22 12:16:55 (-0400) Started service 'api sha256:3a7cfdf9acc4452a3a50211e5b1b4cdda7a017d6e7501ed11896f23d82c49aa2' ``` ---
**Author:** ![alanb128](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alanb128/32/2839_2.png) [@alanb128](https://forums.balena.io/u/alanb128)\ **Post date:** [April 27, 2022, 6:36pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/2 "2022-04-27T18:36:16Z")
Hello @jack-s what you are describing may have been related to this incident: [Balena.io Status - Image deltas are not being generated.](https://status.balena.io/incidents/cnd0f1yml36n) which has since been resolved. Are you still experiencing release downloading issues? ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [April 27, 2022, 7:00pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/3 "2022-04-27T19:00:46Z")
@alanb128 The “Delta still processing remotely” messages in the attached logs may have been related to the referenced incident but the bug I am trying to show is unrelated. I do not have downloading issues when the container is not running. When the container is running, the memory and cpu usage of the pi zero 2 is too high and causes issues. I tried to use the “fleet update strategy” variable to stop the container before downloading but that is not working. The call to kill the service comes after the image is downloaded. I tried to show that with the logs by stopping the container manually, changing the release to trigger the process, and then showing that the call to kill the service (at 12:16:41) comes after the download starts (at 12:11:02). Thanks ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [April 27, 2022, 7:07pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/4 "2022-04-27T19:07:25Z")
Here are another set of logs that show the same problem. Luckily, this download went smoothly even though the container was running but the logs still show that the host did not follow the “kill-then-download” strategy. In this case, I changed the fleet-wide pinned release but the host still downloaded the image before killing the running service. The first two log lines are output from the running container. The line at (14:54:04) shows that the next release downloaded started. The call to kill the service isn’t logged until line five (14:56:34), after the image has been downloaded (14:56:33). ```auto 27.04.22 14:53:50 (-0400) api ======== Running on http://0.0.0.0:80 ======== 27.04.22 14:53:50 (-0400) api (Press CTRL+C to quit) 27.04.22 14:54:04 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:56:33 (-0400) Downloaded image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:56:34 (-0400) Killing service 'api sha256:f739d5f084b14b4e4a022ee1bcc46832b8be7350f25d03d8fc8fa46514927010' 27.04.22 14:56:46 (-0400) Service exited 'api sha256:f739d5f084b14b4e4a022ee1bcc46832b8be7350f25d03d8fc8fa46514927010' 27.04.22 14:56:47 (-0400) Killed service 'api sha256:f739d5f084b14b4e4a022ee1bcc46832b8be7350f25d03d8fc8fa46514927010' 27.04.22 14:56:48 (-0400) Deleting image 'registry2.balena-cloud.com/v2/c8544ad2ec434346a4a8e31d69e213f9@sha256:412ffbd48828a95b21d7a6a65e7469c0bbdcd721e75740beb9eda6876d16c489' 27.04.22 14:57:04 (-0400) Deleted image 'registry2.balena-cloud.com/v2/c8544ad2ec434346a4a8e31d69e213f9@sha256:412ffbd48828a95b21d7a6a65e7469c0bbdcd721e75740beb9eda6876d16c489' 27.04.22 14:57:05 (-0400) Installing service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 14:57:07 (-0400) Installed service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 14:57:07 (-0400) Starting service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 14:57:09 (-0400) Started service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' ``` ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [April 27, 2022, 7:21pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/5 "2022-04-27T19:21:23Z")
Here are the logs from a different device in the same fleet that is having an issue downloading the same release. Both devices started from the same release, are on the same wifi network, and are physically sitting next to each other. This device currently reports memory usage as 362 MB / 411 MB. It seems that stopping the container before download decreases the memory and CPU usage enough that the download happens smoothly. ```auto 27.04.22 14:43:21 (-0400) api ======== Running on http://0.0.0.0:80 ======== 27.04.22 14:43:21 (-0400) api (Press CTRL+C to quit) 27.04.22 14:47:45 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:48:41 (-0400) Delta still processing remotely. Will retry... 27.04.22 14:48:42 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:49:38 (-0400) Delta still processing remotely. Will retry... 27.04.22 14:49:39 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:55:08 (-0400) Failed to download image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' due to 'connect ECONNREFUSED /var/run/balena-engine.sock' 27.04.22 14:55:52 (-0400) Supervisor starting 27.04.22 14:55:54 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 14:56:13 (-0400) Supervisor starting 27.04.22 14:56:15 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 15:02:42 (-0400) Failed to download image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' due to 'connect ECONNREFUSED /var/run/balena-engine.sock' 27.04.22 15:03:23 (-0400) Supervisor starting 27.04.22 15:03:24 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 15:03:46 (-0400) Supervisor starting 27.04.22 15:03:47 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 15:10:01 (-0400) Failed to download image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' due to 'connect ECONNREFUSED /var/run/balena-engine.sock' 27.04.22 15:10:43 (-0400) Supervisor starting 27.04.22 15:10:45 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 15:11:03 (-0400) Supervisor starting 27.04.22 15:11:05 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' ``` ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [April 27, 2022, 8:12pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/6 "2022-04-27T20:12:10Z")
This is actually just a documentation problem. I found [an issue in the balena-supervisor Github](https://github.com/balena-os/balena-supervisor/issues/1233) that referenced this and the steps to reproduce said to use `RESIN_SUPERVISOR_UPDATE_STRATEGY`. When I set `RESIN_SUPERVISOR_UPDATE_STRATEGY=kill-then-download`, the supervisor kills the service before beginning the download as expected. In the [Balena documentation page for fleet update strategy](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/) that was mentioned in the original post, the references to configuration `BALENA_SUPERVISOR_UPDATE_STRATEGY` should be changed to `RESIN_SUPERVISOR_UPDATE_STRATEGY`. For completeness, here are the logs of the device with the proper configuration variable name set which show the “Killing service” message before the “Downloading image” message. ```auto 27.04.22 16:08:28 (-0400) api ======== Running on http://0.0.0.0:80 ======== 27.04.22 16:08:28 (-0400) api (Press CTRL+C to quit) 27.04.22 16:08:39 (-0400) Killing service 'api sha256:d07224f598b3340b4d8aff35a5cf703fd4cc2b62eccc4747f582664ace3cd802' 27.04.22 16:08:51 (-0400) Service exited 'api sha256:d07224f598b3340b4d8aff35a5cf703fd4cc2b62eccc4747f582664ace3cd802' 27.04.22 16:08:51 (-0400) Killed service 'api sha256:d07224f598b3340b4d8aff35a5cf703fd4cc2b62eccc4747f582664ace3cd802' 27.04.22 16:08:52 (-0400) Downloading delta for image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 16:10:48 (-0400) Downloaded image 'registry2.balena-cloud.com/v2/d42ffa7e55694652a7e02eb37ab50a82@sha256:bf0124ff6d15aa698a6a4a3ded5f690b2fcbf44cc1e4151995f97aa591ff8a26' 27.04.22 16:10:50 (-0400) Deleting image 'registry2.balena-cloud.com/v2/6124c6e4e354be2d11ea065ee8123bb6@sha256:5b4489134e8b241cf2653e739b8cac7120f713ea7d274fd47b46a3c801f070df' 27.04.22 16:10:56 (-0400) Deleted image 'registry2.balena-cloud.com/v2/6124c6e4e354be2d11ea065ee8123bb6@sha256:5b4489134e8b241cf2653e739b8cac7120f713ea7d274fd47b46a3c801f070df' 27.04.22 16:10:57 (-0400) Installing service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 16:10:58 (-0400) Installed service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 16:10:58 (-0400) Starting service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' 27.04.22 16:11:00 (-0400) Started service 'api sha256:5d8bfcb99a1e2d655c6c7da2bebecf5aab4a3795cc5b610068e6e465694d2307' ``` ---
**Author:** ![vipulgupta2048](https://avatars.discourse-cdn.com/v4/letter/v/a183cd/32.png) [@vipulgupta2048](https://forums.balena.io/u/vipulgupta2048)\ **Post date:** [May 3, 2022, 8:09am UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/10 "2022-05-03T08:09:15Z")
Hello, Thanks for your continued investigation and feedback on this issue. It is very valuable. The update strategy documentation at the moment doesn’t clearly reference which strategy works with which supervisor version correctly. I feel like that’s what’s happening here. In your case, the configuration option `BALENA_SUPERVISOR_UPDATE_STRATEGY ` isn’t probably supported by the supervisor running on the device. Please tell us the balenaOS and Supervisor version that is running on the Pi zero 2 where you ran these tests. Since this a newly released device, it’s weird that SV is having this issue at all. Regardless, the intention of the documentation is correct to refer to `BALENA_SUPERVISOR_UPDATE_STRATEGY ` everywhere since that’s what we intend to support long term. Actions I intend to take ahead: 1. Open a GitHub issue on the SV repo similar to one you referenced. 2. Check if we can add some version information to the docs to better inform users of what configuration they should apply. I apologize for the inconvenience you had to face and we take feedback very seriously. Rest assured, we will get this sorted and inform you as the issue progresses. Please do let us know if there’s something else we can help you with. Thanks again. ---
**Author:** ![vipulgupta2048](https://avatars.discourse-cdn.com/v4/letter/v/a183cd/32.png) [@vipulgupta2048](https://forums.balena.io/u/vipulgupta2048)\ **Post date:** [May 3, 2022, 8:29am UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/12 "2022-05-03T08:29:42Z")
I have opened the issue here: [Kill-then-download strategy isn't killing the containers with BALENA\_SUPERVISOR\_UPDATE\_STRATEGY · Issue #1939 · balena-os/balena-supervisor · GitHub](https://github.com/balena-os/balena-supervisor/issues/1939) and linked it to this thread. This also references the documentation suggestion you provided us with. Do tell the balenaOS and Supervisor version running on the device even support access if you can for us to test and reproduce as well. It would be incredibly helpful. Thanks! ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [May 3, 2022, 1:43pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/14 "2022-05-03T13:43:35Z")
That makes sense. Sorry I should’ve sent the balenaOS and supervisor versions in the original post. All devices are Raspberry Pi Zero 2 W running balenaOS 2.94.4 development with supervisor version 13.0.0. Most were created on 2022-03-08. Thanks for the responses! ---
**Author:** ![lmbarros](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/lmbarros/32/5710_2.png) [@lmbarros](https://forums.balena.io/u/lmbarros)\ **Post date:** [May 19, 2022, 6:53pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/16 "2022-05-19T18:53:08Z")
Hi There! From what I followed on the GitHub issue, I believe that using the new, per-container update strategy has solved your problem, right? Please let us know if there’s still something we can do for you with regards to this issue! For future visitors of this thread: the current preferred approach to configure the update strategy is by setting the `io.balena.update.strategy` label on the desired services. The older mechanism (based on configuration variables) is deprecated. We have updated our docs with this information: [Fleet update strategy - Balena Documentation](https://www.balena.io/docs/learn/deploy/release-strategy/update-strategies/) ---
**Author:** ![jack\_s](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@jack\_s](https://forums.balena.io/u/jack_s)\ **Post date:** [May 20, 2022, 1:33pm UTC](https://forums.balena.io/t/update-strategy-with-single-device/356886/18 "2022-05-20T13:33:00Z")
Yes, putting the update strategy in the docker compose file works. Thanks.