We’re building and deploying our images from our CI with
balena deploy, and for multiple releases now the deploy has succeeded (exit code 0) with multiple of the following messages:
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: An image does not exist locally with the tag: registry2.balena-cloud.com/v2/[hash removed] at Stream.<anonymous> (/snapshot/versioned-source/node_modules/docker-progress/index.js:53:19) at Stream.emit (events.js:198:13) at Stream.EventEmitter.emit (domain.js:448:20) at drain (/snapshot/versioned-source/node_modules/through/index.js:36:16) at Stream.stream.queue.stream.push (/snapshot/versioned-source/node_modules/through/index.js:45:5) at Parser.exports.parse.parser.onToken (/snapshot/versioned-source/node_modules/JSONStream/index.js:132:18) at Parser.proto.write (/snapshot/versioned-source/node_modules/jsonparse/jsonparse.js:135:34) at Stream.<anonymous> (/snapshot/versioned-source/node_modules/JSONStream/index.js:23:12) at Stream.stream.write (/snapshot/versioned-source/node_modules/through/index.js:26:11) at IncomingMessage.ondata (_stream_readable.js:708:20) at IncomingMessage.emit (events.js:198:13) at IncomingMessage.EventEmitter.emit (domain.js:448:20) at addChunk (_stream_readable.js:287:12) at readableAddChunk (_stream_readable.js:268:11) at IncomingMessage.Readable.push (_stream_readable.js:223:10) at HTTPParser.parserOnBody (_http_common.js:122:22)
It creates a new release, however, and when our devices try to pull it, a number of the image pulls fail with 404 errors, which would seem to correspond to the ones that failed in the deploy. There are many very large images being deployed, so maybe the infrastructure can’t handle it, but the errors aren’t even being detected. Luckily we’re still in testing, because it’d be pretty bad if Balena pushed broken releases to the field.