At first I thought just patience was in order, but after several hours, the devices still get the same error when trying to update. Any thoughts on how to resolve?
Hi Brant, sorry for the delay.
I have just looked at your device. Looking through our knowledge base there seem to be cases when this is caused by the software deployment process rather than by the device. In this case pushing a new release often solves the problem. Have you tried pushing a new - basically unchanged - release of your application ?
Cheers Thomas
Yes, when I first had the issue, I waited 1/2 hr then pushed another update. So that we are currently 2 updates behind. Should I simply push a 3rd to see what happens?
You could try that but I think I will have to take another look at the device what else I can see from logs. Would you please re-enable support access for me?
I most certainly can, enabled for 6hrs this time. I am testing 2 devices with this app and they are experiencing the same issue. So I suspect that build image might not be getting published. The other device is 65d055319cfd7b0d2b067f578a52996c, also with support access enabled. Thanks again.
I have just learnt that this might be connected to a known but yet unresolved issue.
As a fix you could try disabling delta updates on the affected devices. You will possibly have to reboot them after doing so.
That was it. Disabling deltas fixed the update problem.
It did transition into a surprising permission error on my entrypoint.sh script through that’s preventing the container from starting. But I should be able to make progress again!
@samothx
We are having the same problem on my Balena application.
We tried to deploy a new image, but we can’t solve.
Is this a specific application problem? or our image problem?
We have another application which the same image is deployed, but we didn’t have problem on that application.
So, I think this caused by Balena application.
Hello, I am having the same problem as that originally described. Can balenaCloud please take a look at what the problem might be? My application ID is 1665575 and device UUID is ca908a241e00dd55a9620b29d1205e4c with this setup: Host OS version: balenaOS 2.38.0+rev1 (production), Supervisor version 9.15.7. I have granted support access. Device type is QEMU run with more or less defaults suggested by Balena:
The device is hardwired to fibre Internet, and had no problem downloading the first image after the factory build. Every subsequent build release shows download to about 50% of the image and then restarts the download with the same error. What can I do to understand this problem? Enabling or disabling delta updates does not appear to help.
16.08.20 18:31:31 (+0200) Downloading image 'registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0'
16.08.20 18:32:12 (+0200) Failed to download image 'registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0' due to '(HTTP code 404) no such image - no such image: registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0: No such image: registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0 '
16.08.20 18:32:16 (+0200) Downloading image 'registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0'
16.08.20 18:33:14 (+0200) Failed to download image 'registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0' due to '(HTTP code 404) no such image - no such image: registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0: No such image: registry2.balena-cloud.com/v2/b05730ffe715cddd74aac6df393d99d6@sha256:def4b20fa5e219d0bbd0c7ef9bc8280349be67f4baf25ac6f474163c60ff25d0 '
Using details from another post image fails to download 404 no such image the problem is now apparent. It would be great if the log messages made this more apparent, but at least I understand the problem now.
Aug 17 18:42:33 ca908a2 balenad[624]: time="2020-08-17T18:42:33.332271658Z" level=info
msg="Attempting next endpoint for pull after error: failed to register layer: Error processing tar file(exit status 1):
write /usr/lib/python3.6/html/entities.py: no space left on device"