container
Last updated
Was this helpful?
Last updated
Was this helpful?
Provides the container
actions and module type.Note that this provider is currently automatically included, and you do not need to configure it in your project configuration.
Below is the full schema reference for the provider configuration..
The reference is divided into two sections. The contains the complete YAML schema, and the describes each schema key.
The values in the schema below are the default values.
providers[]
array[object]
[]
No
providers[].name
The name of the provider plugin to use.
string
Yes
Example:
providers[].dependencies[]
List other providers that should be resolved before this one.
array[string]
[]
No
Example:
providers[].environments[]
If specified, this provider will only be used in the listed environments. Note that an empty array effectively disables the provider. To use a provider in all environments, omit this field.
array[string]
No
Example:
providers[].dockerBuildExtraFlags[]
Extra flags to pass to the docker build
command. Will extend the spec.extraFlags
specified in each container Build action.
array[string]
No
providers[].gardenContainerBuilder
object
No
providers[].gardenContainerBuilder.enabled
Enable Remote Container Builder, which can speed up builds significantly using fast machines and extremely fast caching. When the project is connected and you're logged in to https://app.garden.io the container builder will be enabled by default.
Under the hood, enabling this option means that Garden will install a remote buildx driver on your local Docker daemon, and use that for builds. See also https://docs.docker.com/build/drivers/remote/
In addition to this setting, the environment variable GARDEN_CONTAINER_BUILDER
can be used to override this setting, if enabled in the configuration. Set it to false
or 0
to temporarily disable Remote Container Builder.
If service limits are reached, or Remote Container Builder is not available, Garden will fall back to building images locally, or it falls back to building in your Kubernetes cluster in case in-cluster building is configured in the Kubernetes provider configuration.
Please note that when enabling Container Builder together with in-cluster building, you need to authenticate to your deploymentRegistry
from the local machine (e.g. by running docker login
).
boolean
false
No
> name
> dependencies
> environments
> dockerBuildExtraFlags
> gardenContainerBuilder
> > enabled