Docker build Components allow you to build an existing Dockerfile in a public or connected repo, and sync it into your customer installs.

​
Configuring a Docker build Component

To configure a Docker build Component, specify a repo, the required build paramaters and Dockerfile path.
nuon.<your-app>.toml
[[components]]
name       = "app_image"
type       = "docker_build"
dockerfile = "Dockerfile"
[components.connected_repo]
directory = "components/app-image"
repo      = "<your-app>"
branch    = "main"
You can configure Docker build Components to use either a public repo (using a public_repo block) or a private GitHub repo (using a connected_repo block). Read more about VCS configuration here.

​
Deployments

Docker build Components cannot be deployed directly in a customer install. When an image is released, it will be synced into the customer install and made available to other Components via variables. To deploy a Docker build component, reference the image from a Helm Component or Terraform Component:
nuon.<your-app>.toml
[[components]]
name       = "eks_deployment"
type       = "helm_chart"
chart_name = "<your-app>"
[components.connected_repo]
repo      = "<your-app>"
directory = "components/helm-chart"
branch    = "main"
[components.values]
"env.IMAGE_TAG"        = "{{.nuon.components.app_image.image.tag}}"
"env.IMAGE_REPOSITORY" = "{{.nuon.components.app_image.image.repository.uri}}"

[[components]]
name              = "ecs_service"
type              = "terraform_module"
terraform_version = "1.11.3"
[components.connected_repo]
repo      = "<your-app>"
directory = "components/ecs-service"
branch    = "main"
[components.vars]
"image_tag"        = "{{.nuon.components.app_image.image.tag}}"
"image_repository" = "{{.nuon.components.app_image.image.repository.uri}}"

[[components]]
name      = "eks_job"
type      = "job"
image_url = "{{.nuon.components.app_image.image.repository.uri}}"
tag       = "{{.nuon.components.app_image.image.tag}}"

​
Image Syncing

When a Docker build Component is released, Nuon will automatically sync the image into the end customer account. This image is stored in a local registry that is provisioned in the customer account. Nuon image syncing allows you to sync images into accounts, without worrying about cross account permissions, registry authentication or publishing public images. Any Dockerfile in a repo can be built, and synced. The sync process works by creating a 1-time authentication flow that grants the Install Runner access to pull the image from the org data plane, and copy it into the local registry.

​
Build Arguments and Environment Variables

You can specify custom build arguments and environment variables to be used when building an image:
If you have custom build requirements, we recommend building your images from within your own CI/CD platform, and using a container image to import them.