# Remote Container Builder

The Remote Container Builder enables you to build container images using **blazing-fast, remote build compute instances** managed by Garden. Each built layer of your Dockerfile is stored on low-latency, high-throughput NVMe storage so that your entire team can benefit from shared build caches. This can result in [significantly faster builds](https://garden.io/blog/oem-cloud-builder).

Our free-tier includes a certain amount of build minutes and GBs of layer caching per month and you get more by switching to our team or enterprise tiers. You can learn more about the [different tiers here](https://garden.io/plans).

You can also use the [Builds UI](https://app.garden.io) to view build logs and analyze bottlenecks in your builds.

<figure><picture><source srcset="https://public-assets-for-docs-site.s3.eu-central-1.amazonaws.com/builds-detail-dark.png" media="(prefers-color-scheme: dark)"><img src="https://public-assets-for-docs-site.s3.eu-central-1.amazonaws.com/builds-detail.png" alt="Build details"></picture><figcaption><p>Build details</p></figcaption></figure>

### Using the Remote Container Builder

To use the Remote Container Builder you need to first [connect your project to the Garden Cloud backend](https://docs.garden.io/docs-edge/guides/connecting-project).

Then you need to enable it in your project level Garden configuration by adding the following provider config:

```yaml

  - name: container
    gardenContainerBuilder:
      enabled: true
```

You can learn more about [enabling the Remote Container Builder here](https://docs.garden.io/docs-edge/using-garden-with/containers/using-remote-container-builder).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.garden.io/docs-edge/features/remote-container-builder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.