# Using Remote Container Builder

The [Remote Container Builder](/docs-edge/features/remote-container-builder.md) enables you to build container images using **blazing-fast, remote build compute instances** managed by Garden and to share build caches with your team.

Our free-tier includes a certain amount of build minutes and 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).

If you run out of build minutes, Garden will simply fallback to local builds without any disruption.

### Enabling Remote Container Builder

#### Step 1 — Log in to Garden Cloud

You need to be logged into Garden Cloud to use the remote container builder:

```sh
garden login
```

If this is your first time logging in, you'll be asked to sign up.

#### Step 2 — Configure the `container` provider

To enable the Remote Container Builder, add the following to your project level configuration under the `provider` field:

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

Afterwards your project config should look something like this:

```yaml
kind: Project
name: my-project
environments:
  - name: dev
  - name: ci

providers:
  - name: container
    gardenContainerBuilder:
      enabled: true
  - name: kubernetes
    # ...
```

You can also enable the Remote Container Builder in specific environments like so:

```yaml
kind: Project
name: my-project
environments:
  - name: local
  - name: remote-dev
  - name: ci

providers:
  - name: container
    environments: [remote-dev, ci] # <-- Specify the environment
    gardenContainerBuilder:
      enabled: true
  - name: kubernetes
    # ...
```

#### Step 3 — Give it a spin (optional)

If you a already have a Garden project with `container` Build actions, simply run:

```
garden build
```

...or any other command that triggers a build.

If you're using the `kubernetes` provider, the image will be pushed to the configured `deploymentRegistry`.

You can then check out the results in the [new Builds UI](https://app.garden.io).

### Next steps

If you haven't already, check out our docs on [building containers](/docs-edge/using-garden-with/containers/building-containers.md) to learn how to add `container` Build actions to your project that can be built by the Remote Container Builder and used by other actions, e.g. to:

* [Deploy K8s resources](/docs-edge/using-garden-with/kubernetes/deploy-k8s-resource.md)
* [Install Helm charts](/docs-edge/using-garden-with/kubernetes/install-helm-chart.md)
* [Run tests](/docs-edge/using-garden-with/kubernetes/run-tests-and-tasks.md)


---

# 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/using-garden-with/containers/using-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.