Using Remote Container Builder
Last updated
Was this helpful?
Last updated
Was this helpful?
The 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 .
If you run out of build minutes, Garden will simply fallback to local builds without any disruption.
You need to be logged into Garden Cloud to use the remote container builder:
If this is your first time logging in, you'll be asked to sign up.
container provider (optional)The Remote Container Builder is enabled by default once you've logged in, so no further configuration is required.
If you want more granular control and e.g. only enable the container builder in certain environments you can do that via container provider in your project level configuration.
For example:
If you a already have a Garden project with container Build actions, simply run:
...or any other command that triggers a build.
If you're using the kubernetes provider, the image will be pushed to the configured deploymentRegistry.
Your container actions will be built by the container builder and can be used by other actions, e.g. to:
You can then check out the results in the .
If you haven't already, check out our docs on to learn how to add container Build actions to your project. Note that the Remote Container Builder also supports !