Search…
Building Docker Images
Release allows you to build Docker images for your Helm charts. You can define any number Docker builds for your application. The Dockerfiles must exist in the application's source control repository. You can not specify Docker builds from remote source control repositories.
1
builds:
2
- name: nginx
3
dockerfile: Dockerfile
4
context: nginx
5
args:
6
- MAX_UPLOAD_SIZE=60
7
- name: backend
8
dockerfile: Dockerfile-backend
9
context: app
Copied!
Example Docker builds for a custom ngnix and backend containers

Build Environment Variables

Each container built by Release will generate environment variables that can be used in your Helm charts. By default Release adds environment variables for the Docker registry and path to the image built.
1
- key: RELEASE_REGISTRY_ENDPOINT
2
value: 123456789000.dkr.ecr.us-east-1.amazonaws.com
3
secret: false
4
- key: RELEASE_REGISTRY_PATH
5
value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app
6
secret: false
Copied!
Each container build will generate environment variables that can be used in your Helm charts. Two environment variables are emitted per build. The ngnix build shown in the first example will generate NGINX_REGISTRY_IMAGE_URLandNGINX_REGISTRY_IMAGE_SHA
1
- key: NGINX_REGISTRY_IMAGE_URL
2
value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app/[email protected]:f1e8b983e8f842170caed5ce76fa92171acfc0f8296283c85155771374adec9c
3
secret: false
4
- key: NGINX_REGISTRY_IMAGE_SHA
5
value: f1e8b983e8f842170caed5ce76fa92171acfc0f8296283c85155771374adec9c
6
- key: BACKEND_REGISTRY_IMAGE_URL
7
value: 123456789000.dkr.ecr.us-east-1.amazonaws.com/acme-org/acme-app/[email protected]:4852bafb7f7cf76375d0e090f737926210de462ef35c9f9616f8a2e17ebb0dda
8
secret: false
9
- key: BACKEND_REGISTRY_IMAGE_SHA
10
value: 4852bafb7f7cf76375d0e090f737926210de462ef35c9f9616f8a2e17ebb0dda
11
secret: false
Copied!
Example of generated build environment variables.