> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-upload-an-artifact.md).

# Build and push artifacts and images

There are many ways you can use Harness CI to upload artifacts.

## What you will learn from this topic

* How to build and push images to container registries using Build and Push steps
* How to store artifacts with a Harness CI pipeline execution
* How to upload artifacts to cloud storage using Upload Artifact steps
* How to download artifacts into your pipeline workspace

## Before you begin

* **Harness CI pipeline**: You need a Harness CI pipeline with a build stage configured.
* **Container registry connector**: You need a connector for your target container registry or cloud storage provider.

You can use Harness CI to build image, push image, and upload artifacts, such as Docker images or test results. [Build and Push steps](#build-and-push) build your codebase and then push the resulting artifact to a container registry or cloud storage repo. [Upload Artifact steps](#upload-artifacts) upload any artifact.

To store files and folders with the pipeline execution without configuring external storage, go to [Artifacts](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/artifacts.md).

### Build and push <a href="#build-and-push" id="build-and-push"></a>

Build and Push steps build your codebase and then push the artifact to a repo. You can:

* [Build and push to Docker Hub or a Docker registry](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-docker-registry.md)
* [Build and push to Azure Container Registry (ACR)](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-acr.md)
* [Build and push to Amazon Elastic Container Registry (ECR)](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-ecr-step-settings.md)
* [Build and push to Google Artifact Registry (GAR)](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-gar.md)
* [Build and push to GitHub Container Registry (GHCR)](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-ghcr.md)
* [Build and push to a JFrog Artifactory Docker registry](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-docker-jfrog.md)

For other non-Docker upload locations, you can use a script in a [Run step](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/run-step-settings.md) to build and upload the artifact.

{% hint style="info" %}
You can also:

* [Build images without pushing](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-without-push.md)
* [Build multi-architecture images](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-multi-arch.md)
* [Use Docker Buildx Bake for advanced multi-registry builds](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/docker-buildx-bake.md)
  {% endhint %}

<details>

<summary>Video: Add a Build and Push step</summary>

The following video demonstrates how to add a **Build and Push** step to a Harness CI pipeline.

{% embed url="<https://www.youtube.com/embed/v3A4kF1Upqo?feature=oembed>" %}

</details>

### Kubernetes cluster build infrastructures require root access <a href="#kubernetes-cluster-build-infrastructures-require-root-access" id="kubernetes-cluster-build-infrastructures-require-root-access"></a>

With Kubernetes cluster build infrastructures, Build and Push steps use [Chainguard's maintained Kaniko fork](https://github.com/chainguard-forks/kaniko/blob/main/README.md). Other build infrastructures use [drone-docker](https://github.com/drone-plugins/drone-docker/blob/master/README.md). Kaniko can run as non-root in many cases. Root access is only required when your Dockerfile performs privileged operations (e.g., installing system packages, modifying root-owned directories).

If your build runs as non-root (`runAsNonRoot: true`), and you want to run the Build and Push step as root, you can set **Run as User** to `0` on the Build and Push step to use the root user for that individual step only.

If your security policy does not allow running as root, go to [Build and push with non-root users](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push-nonroot.md).

### Pull images <a href="#pull-images" id="pull-images"></a>

You can pull and run images in your pipelines by declaring them in your steps' Image setting. For example, you could pull and run an image in a [Background step](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/manage-dependencies/background-step-settings.md) or [Run step](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/run-step-settings.md).

### Upload artifacts <a href="#upload-artifacts" id="upload-artifacts"></a>

Upload Artifacts steps upload artifacts. These steps *do not* include build commands. You can:

* [Upload artifacts to JFrog Artifactory non-Docker registries](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-jfrog.md)
* [Upload artifacts to GCS](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-gcs-step-settings.md)
* [Upload artifacts to S3](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-s3.md)
* [Upload artifacts to Sonatype Nexus](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-sonatype-nexus.md)
* [Upload Helm charts to container registries](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-helm-chart.md)
* [Send artifacts by email](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/drone-email-plugin.md)
* Run any upload script in a [Run step](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/run-step-settings.md) or [use plugins](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/use-drone-plugins/explore-ci-plugins.md).

{% hint style="info" %}
**ARTIFACTS TAB**

Regardless of how you upload artifacts, you can [publish any artifact URL to the Artifacts tab](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/artifacts-tab.md).
{% endhint %}

### Download artifacts <a href="#download-artifacts" id="download-artifacts"></a>

You can use Run steps and Plugin steps to download artifacts into your pipeline workspace.

For example:

* [Download artifacts from GCS](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-gcs-step-settings.md#download-artifacts-from-gcs)
* [Download artifacts from S3](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-s3.md#download-artifacts-from-s3)
* [Use the Download plugin](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/use-drone-plugins/run-a-drone-plugin-in-ci.md)
* [Run any script in a Run step](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/run-step-settings.md)
* [Manage dependencies](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/manage-dependencies.md)
* [Caching and data sharing](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/caching-ci-data.md)

## Troubleshooting

<details>

<summary>What drives the Build and Push steps? What is kaniko?</summary>

Go to [CI Knowledge Base](https://developer.harness.io/continuous-integration/troubleshooting-and-resources/ci-articles-and-faqs/continuous-integration-faqs.md#what-drives-the-build-and-push-steps-what-is-kaniko).

</details>

<details>

<summary>Can I run Build and Push steps as root if my build infrastructure runs as non-root?</summary>

Go to [CI Knowledge Base](https://developer.harness.io/continuous-integration/troubleshooting-and-resources/ci-articles-and-faqs/continuous-integration-faqs.md#can-i-run-build-and-push-steps-as-root-if-my-build-infrastructure-runs-as-non-root).

</details>

<details>

<summary>Build and Push to ECR step fails with error building image, failed to execute command, exec format error.</summary>

Go to [CI Knowledge Base](https://developer.harness.io/continuous-integration/troubleshooting-and-resources/ci-articles-and-faqs/continuous-integration-faqs.md#build-and-push-to-ecr-step-fails-with-error-building-image-failed-to-execute-command-exec-format-error).

</details>

<details>

<summary>How do I fix this kaniko container runtime error: kaniko should only be run inside of a container?</summary>

Go to [CI Knowledge Base](https://developer.harness.io/continuous-integration/troubleshooting-and-resources/ci-articles-and-faqs/articles/kaniko-container-runtime-error.md).

</details>

## Next steps

* Go to [Artifacts](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/artifacts.md) to store, preview, and download files produced by a CI execution.
* Go to [Build and push to Docker registry](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-docker-registry.md) to build and push images to Docker Hub.
* Go to [Upload artifacts to S3](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-s3.md) to upload artifacts to Amazon S3.
* Go to [Publish anything to the Artifacts tab](https://developer.harness.io/continuous-integration/use-harness-ci/use-harness-ci/build-and-upload-artifacts/artifacts-tab.md) to display artifact links in the build UI.

{% @harness-feedback/feedback %}
