I’m attempting to create a new release with a command that I’ve been using successfully for the last several years.
balena deploy edo/development --registry-secrets=../../credentials.yml --build --debug
Regardless of what I try, I’ve been getting Deploy failed
with the following error…
Unable to extract image digest (content hash) from image upload progress stream for image:
registry2.balena-cloud.com/v2/d408ca4c4855811636fc5c3cefe699d9:latest
ExpectedError: Unable to extract image digest (content hash) from image upload progress stream for image:
registry2.balena-cloud.com/v2/d408ca4c4855811636fc5c3cefe699d9:latest
at pushImage (C:\Program Files\balena-cli\client\build\utils\compose_ts.js:698:23)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Promise.all (index 1)
at async inspectAndPushImage (C:\Program Files\balena-cli\client\build\utils\compose_ts.js:710:42)
at async Promise.all (index 4)
at async pushAndUpdateServiceImages (C:\Program Files\balena-cli\client\build\utils\compose_ts.js:739:9)
at async pushServiceImages (C:\Program Files\balena-cli\client\build\utils\compose_ts.js:748:5)
at async C:\Program Files\balena-cli\client\build\utils\compose_ts.js:789:17
at async awaitInterruptibleTask (C:\Program Files\balena-cli\client\build\utils\helpers.js:283:16)
at async deployProject (C:\Program Files\balena-cli\client\build\utils\compose_ts.js:787:13)
at async DeployCmd.deployProject (C:\Program Files\balena-cli\client\build\commands\deploy\index.js:146:27)
at async DeployCmd.run (C:\Program Files\balena-cli\client\build\commands\deploy\index.js:50:25)
at async DeployCmd._run (C:\Program Files\balena-cli\client\node_modules\@oclif\core\lib\command.js:312:22)
at async Config.runCommand (C:\Program Files\balena-cli\client\node_modules\@oclif\core\lib\config\config.js:435:25)
at async run (C:\Program Files\balena-cli\client\node_modules\@oclif\core\lib\main.js:95:16)
at async C:\Program Files\balena-cli\client\build\app.js:78:13
I’m running this on a Windows 11 laptop. I’ve completely uninstalled/reinstalled Docker, tried going back to HyperV from WSL 2, tried different networks, and all attempted have yielded the same error.
I see this similar post from a couple months ago, but the ‘solution’ was to use Linux, which to me isn’t a valid solution to the problem.
Any ideas?
Edit: If I use a Linux VM I’m able to deploy this release which to me rules out any configuration errors with the release itself.