<commit_before>---
title: "Kaniko"
meta_description: "Alternative image container build process using Kaniko for Polyaxon."
custom_excerpt: "Polyaxon allows users to build container images using the Kaniko project."
image: "../../content/images/integrations/kaniko.png"
author:
  name: "Polyaxon"
  slug: "Polyaxon"
  website: "https://polyaxon.com"
  twitter: "polyaxonAI"
  github: "polyaxon"
tags: 
  - containers
  - scheduling
featured: true
visibility: public
status: published
---

### Overview

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

You can configure Kaniko as build backend per job/experiment or by as the default build backend.  

## Using Kaniko per job/experiment

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

```yaml
...
build:
  ...
  backend: kaniko
```

## Using Kaniko as the default build backend
In order to deploy Polyaxon with Kaniko as the default backend build option, user need to set `buildBackend` in their Polyaxon deployment config file.

```yaml
...
buildBackend: kaniko
...
```

## Changing the Kaniko image, image tag, and the image pull policy
<commit_msg>Set kaniko to beta<commit_after>---
title: "Kaniko"
meta_description: "Alternative image container build process using Kaniko for Polyaxon."
custom_excerpt: "Polyaxon allows users to build container images using the Kaniko project."
image: "../../content/images/integrations/kaniko.png"
author:
  name: "Polyaxon"
  slug: "Polyaxon"
  website: "https://polyaxon.com"
  twitter: "polyaxonAI"
  github: "polyaxon"
tags: 
  - containers
  - scheduling
featured: true
visibility: public
status: beta
---

### Overview

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

You can configure Kaniko as build backend per job/experiment or by as the default build backend.  

## Using Kaniko per job/experiment

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

```yaml
...
build:
  ...
  backend: kaniko
```

## Using Kaniko as the default build backend
In order to deploy Polyaxon with Kaniko as the default backend build option, user need to set `buildBackend` in their Polyaxon deployment config file.

```yaml
...
buildBackend: kaniko
...
```

## Changing the Kaniko image, image tag, and the image pull policy

{'fraction_non_alphanumeric': 0.08237105465742879, 'fraction_numerical': 0.0, 'mean_word_length': 4.218875502008032, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6482337', 'n_tokens_mistral': 741, 'n_tokens_neox': 696, 'n_words': 329}