# Building from private base images

**URL:** <https://forums.balena.io/t/building-from-private-base-images/943>\
**Category:** Product support\
**Created:** [May 11, 2017, 1:28pm UTC](https://forums.balena.io/t/building-from-private-base-images/943 "2017-05-11T13:28:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![memolipd](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/memolipd/32/310_2.png) [@memolipd](https://forums.balena.io/u/memolipd)\
**Post date:** [May 11, 2017, 1:28pm UTC](https://forums.balena.io/t/building-from-private-base-images/943/1 "2017-05-11T13:28:18Z")

</div>

Hi,

We have a complex system which produces our own base images from resin’s base images.

We host all our base images ourselves but the resin builders don’t have our registry details.

This means our quite valuable base images have to be made public :S is there any way we can pass the builders credentials? or even better already built images?

---

<div class="post-metadata">

**Author:** ![imrehg](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/imrehg/32/36_2.png) [@imrehg](https://forums.balena.io/u/imrehg)\
**Post date:** [May 11, 2017, 4:56pm UTC](https://forums.balena.io/t/building-from-private-base-images/943/2 "2017-05-11T16:56:36Z")

</div>

Maybe you can give a try to resin local build and deploy. Check out the [resin cli](https://github.com/resin-io/resin-cli), and the `resin build` and `resin deploy` commands. These are pretty new and still working on them, hence the lack of big announcement, but if you want to give it a try and give us some feedback, that would be great! 🏂

The `resin build` command builds your container with your local Docker, and `resin deploy` sends an image directly to our services without going through the builders. 📦

---

<div class="post-metadata">

**Author:** ![memolipd](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/memolipd/32/310_2.png) [@memolipd](https://forums.balena.io/u/memolipd)\
**Post date:** [May 12, 2017, 4:21pm UTC](https://forums.balena.io/t/building-from-private-base-images/943/3 "2017-05-12T16:21:09Z")

</div>

now that is some voodoo magic.

Works perfectly.

we have a yarn install inside our dockerfile - am I correct in thinking it’ll retrieve the correct architect from sources? (armv7 while I’m building from my laptop x86)

Awesome.

---

<div class="post-metadata">

**Author:** ![imrehg](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/imrehg/32/36_2.png) [@imrehg](https://forums.balena.io/u/imrehg)\
**Post date:** [May 12, 2017, 4:32pm UTC](https://forums.balena.io/t/building-from-private-base-images/943/4 "2017-05-12T16:32:57Z")

</div>

Yes, by calling `resin build` with the correct application or device-type/architecture combo (see `resin build --help`), it should start to build on the right architecture. Then if you have a matching base image in your `Dockerfile` (the one listed in `FROM resin/.....`), everything will work together, and can build `armv7hf` images on `x86` just fine. ✨

Glad to hear it works, let us know if you have any feedback!
