Hi, I deployed several times today my project using git push balena master However, at some point I suddenly got the following error: [03%20pm] I was reading from your status page that this morning you deployed a fix for a problem related to ARM3: [image] 32bit Arm builds on `arm03`…

I’m getting the same error with a build system that’s unchanged and hasn’t had issues previously. [debug] handling message: {"message":"\u001b[34m[logspout]\u001b[39m (22/22) Installing mercurial (4.9.1-r0)"} [logspout] (22/22) Installing mercurial (4.9.1-r0) [debug] handling message: {…

Thank you for these reports. I have not been able to reproduce the issue myself, but I see some ECONNRESET in builder logs and I have asked our dev ops team to investigate.

I can confirm it’s not working with and without the --emulated flag [Info] Dashboard link: https://dashboard.balena-cloud.com/apps/1477582/devices [debug] handling message: {"message":"\u001b[36m[Info]\u001b[39m Building on arm03"} [Info] Building on arm03 [debug] hand…

The dev ops team has been investigating this issue. It seems to affect only a subset of ARM builds, for some reason – potentially a specific ARM instruction set, or 32 vs 64 bits. We’ll update it here when we know more. Thanks for the reports.

Also affecting my builds (both pushes to a raspberry pi and to an nvidia Tx2). Thank you for the reports :slight_smile: Would it be useful if I put together a miminal Dockerfile that replicates the result? Or is the devps team good to go?

@cnr , if you have something to share, it will be welcome. We’ve got examples of Dockerfiles that fail with base images like “FROM balenalib/raspberrypi3”, and Dockerfiles that succeed with base images like “FROM arm32v7/busybox”, but the key difference it’s not yet clear – it may not even be the bas…

It doesn’t seem to be consistent, at least from my side. I’ve had one deployment succeed, which was simply after several retries. All on RPi3.

The inconsistencies may be a result of our team working on it - we’re still continuing to investigate the issue.

Also having the same issue today, with stable project with only minor source changes. Build fails as shown below: [wificonnect] Step 3/7 : RUN install_packages dnsmasq wireless-tools [wificonnect] ---> Running in f2dc5ab0c4f4 [pigpio] gcc -O3 -Wall -pthread -fpic -c -o pigpio.o pigpio.c …

Hi @chrisys , I understand your team is hard at work on solving the problem - but is there any update on what exactly the issue is or when it might be resolved? I have a project going live in two days and right now I can’t test/deploy to any of my devices…

Problem building - read ECONNRESET

Product support

erlam September 15, 2025, 10:40pm 39

For visibility, I’ve been hitting this issue more recently (sept 15, 2025) and created a topic here: Balena push not working

Topic		Replies	Views
An error occured: read ECONNRESET - airmonitor build Product support	9	1281	August 14, 2019
Balena push not working balenaOS support , docker , network	5	187	September 17, 2025
Deploy failed when trying to deploy on OpenBalena openBalena	18	1330	May 5, 2020
Error: grpc: the connection is unavailable Product support	35	3899	September 3, 2019
Deploy failed when running balena deploy openBalena	6	2609	January 23, 2020

Problem building - read ECONNRESET

Related topics