# Multi Platform Images without buildx **URL:** \ **Category:** General\ **Tags:** docker, build\ **Created:** [April 6, 2023, 10:22am UTC](https://forums.docker.com/t/multi-platform-images-without-buildx/135453 "2023-04-06T10:22:54Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aanandncloudsense](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/aanandncloudsense/32/40147_2.png) [@aanandncloudsense](https://forums.docker.com/u/aanandncloudsense)\ **Post date:** [April 6, 2023, 10:22am UTC](https://forums.docker.com/t/multi-platform-images-without-buildx/135453/1 "2023-04-06T10:22:54Z")
Hi All, Instead of using the experimental buildx feature to build/push multi-platform images (for linux/amd64 & linux/arm64), can we use the `docker build` on corresponding target architecture machines and push them separately to create a manifest with both linux/arm64 & linux/amd64? Thanks, Aanand ---
**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\ **Post date:** [April 6, 2023, 11:22pm UTC](https://forums.docker.com/t/multi-platform-images-without-buildx/135453/2 "2023-04-06T23:22:32Z")
> [@aanandncloudsense](#): > > experimental buildx feature It isn’t experimental. On the other hand, what you are looking for, [`docker manifest`](https://docs.docker.com/engine/reference/commandline/manifest/) is in fact experimental, You can read about both ways in the Docker blog > **[Multi-arch build and images, the simple way | Docker](https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/)** > > ild once, deploy anywhere” is really nice on the paper but if you want to use ARM targets to reduce your bill, such as Raspberry Pis and AWS A1 instances, or even keep using your old i386 servers, deploying everywhere can become a tricky problem as...