New feature: Private Docker images in builds

September 7, 2017

New feature: Private Docker images in builds

Last year we added a feature that lets you build and test your applications before the deployment. We decided to use Docker containers for that, an approach that has many advantages:

  • All builds are isolated in separate containers
  • It's very easy to define your own Docker image (build environment)
  • You can use existing Docker images created by the Docker community

Basing on the feedback from our users, several months later we added an option to build custom images and push them to private repositories, with dedicated support for public Docker Hub, Google Container Registry, and Amazon EC2 Container Registry.

We're happy to announce that you can now use images from private registries in your builds, including Docker Hub, ECR and GCR as well.

Environment tabEnvironment tab

Now you can create a pipeline that will:

  • Build a Docker image on the basis of a dockerfile from the repository and push it to your private registry
  • Build your application in a container launched from the image built in the previous step
  • Deploy the compiled app to your server

Pipeline examplePipeline example

TIP: You can also use Buddy to easily automate your Kubernetes/GKE workflow – for example, apply deployment or run pods/jobs on push to branch.

INFO: You can learn more about building Docker images with Buddy in this article.


Alexander Kus

Alexander Kus

Customer Success Manager

A story-teller and conversation-lover, Alexander decided to invest his skills to help his friends at Buddy transform the cold language of patch notes into exciting narratives. Also: an avid gamer, hip-hop DJ, Liverpool FC fan, absentminded husband, and the father of two.