# Balena cloud/cli builder is still not able to interpret image manifests

**URL:** <https://forums.balena.io/t/balena-cloud-cli-builder-is-still-not-able-to-interpret-image-manifests/43203>\
**Category:** balenaOS\
**Created:** [November 10, 2019, 1:16am UTC](https://forums.balena.io/t/balena-cloud-cli-builder-is-still-not-able-to-interpret-image-manifests/43203 "2019-11-10T01:16:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![matthewcroughan](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/matthewcroughan/32/9424_2.png) [@matthewcroughan](https://forums.balena.io/u/matthewcroughan)\
**Post date:** [November 10, 2019, 4:14am UTC](https://forums.balena.io/t/balena-cloud-cli-builder-is-still-not-able-to-interpret-image-manifests/43203/3 "2019-11-10T04:14:18Z")

</div>

I’ve discovered that there is no solution to this problem, and I cannot continue until it is fixed in Balena or Docker.

It’s a shame, considering this all works locally. ☹

> <https://github.com/moby/moby/issues/36552>
>
> Description
> Before the addition of manifests and multiarch docker hub images, a trivial way to specify an architecture was something like ppc64le/ubuntu:xenial....

---

_[View the full topic](https://forums.balena.io/t/balena-cloud-cli-builder-is-still-not-able-to-interpret-image-manifests/43203)._
