Balena is not able to download delta images for all of the container


I am trying to update the release, its update only few of the container not all.
it was working well, but suddenly the problem has come.

Error logs is this

Delta still processing remotely. Will retry…
Delta still processing remotely. Will retry…
Delta still processing remotely. Will retry…

Downloading delta for image ‘
local-dns-lan [INFO] - 23854 “AAAA IN udp 38 false 512” NOERROR qr,rd,ra 134 0.003640151s
Downloading delta for image ‘
Downloading delta for image ‘
Downloading delta for image '’`

Additional details

root@7943ba9:~# curl -I
HTTP/1.1 301 Moved Permanently
Server: awselb/2.0
Date: Mon, 13 Nov 2023 03:18:33 GMT
Content-Type: text/html
Content-Length: 134
Connection: keep-alive

root@7943ba9:~# nmcli c show
NAME         UUID                                  TYPE      DEVICE      
northbound   0184a25b-7c07-e1af-1d30-4671f06f7479  ethernet  eth0        
southbound   0184a232-232b-ad0c-a2a5-f9d88457330d  ethernet  eth1        
supervisor0  13d8c9ed-7202-4867-859e-7f0dd5263742  bridge    supervisor0 
cellular     0184a266-e20f-1cf1-4476-b86f095bf760  gsm       --          

can you please provide some solution on this or what causing this?

1 Like

+1 Experiencing seemingly the same issue.

1 Like

+1 Also experiencing this. This is a pretty big deal considering we can’t update/change the release on any of our devices.
Running Supervisor 14.1.0 and balenaOS 2.106.7.

@mpous @klutchell sorry to tag you guys but wasn’t sure who to escalate this to. Seems like a pretty big outage (if it is affecting more than just us) as we don’t have another way to update our devices remotely

Hey @trey,

We’re looking into this as a priority. We’ll update you as soon as we can.


A build did finally go through on our end FYI. Thanks for the quick response.

1 Like

@trey @mugeesh

This should all be sorted now. Plus we’ve added instrumentation to detect any errors with deltas much quicker. And we’ll continue to look into and resolve the root cause. Thanks for your patience.:heart:



I’m hitting this issue presently, is there a new incident or could this also be a local phenomenon? I managed to force the update using the method described here, but this is probably not something I would want to do on production