Hi @cnr . From what I understand the ESOCKETTIMEOUT error is due to the git server and builder not being able to connect to the docker socket on the builder. I think the issues were experiencing may have been due to elevated error rate we have been seeing on our ARM Native builders.
The -f flag on git push is essentially rewriting the git history, it by itself should not cause cache invalidation, but perhaps rewriting the app history at the time when the builder and/or API are having issues caused the cache to be invalidated, but its difficult to say. I’ll check with some of the backend team to see if they have any other ideas as to why it would invalidate.
But in general, if you see the ESOCKETTIMEDOUT error, I would first check https://status.balena.io/ to make sure the infrastructure is working correctly and if it is up, I would wait a few minutes or so before pushing again. You shouldn’t ever have to use the -f in these cases and I think if anything it could make things worse