Polyaxon allows users to build container images in-cluster before stating experiment and jobs.


Polyaxon supports multiple backend options to build container images used for running jobs or training experiments.

The native builder is a lightweight container builder, and it's the default backend used in Polyaxon deployment, it has been tested and works smoothly.

If you have changed the default build backend, and you need to use the native builder for some use cases you can follow one of the following options.

If your builds fail in EKS clusters it could be due to DNS resolution, please see this issue. The builds are failing because the latest versions of the AWS EKS-optimized AMI disables the docker bridge network by default. To enable it, add the bootstrap_extra_args parameter to your worker group template.

locals {
  worker_groups = [
      # Other parameters omitted for brevity
      bootstrap_extra_args = "--enable-docker-bridge true"

Using the native builder per job/experiment

In case the default build backend is the not the native builder, users who want to use this native builder to build container images must define explicitly the backend option in their Polyaxon files:

  backend: native

Using the native builder as the default build backend

In order to deploy Polyaxon with the native build backend as the default builder option, users need to either remove or set buildBackend in their Polyaxon deployment config file.

buildBackend: native

By deleting this option as well, you are using the default values, and the native build backend is one of them.