---------------------- To perform a container build action without using the build cache in Garden, you can use the

--force

flag (or

-f

for short) with the

garden build

command. This will force a rebuild of the container, ignoring any existing cache. Here's the command you can use:

garden build --force

Or, for short:

garden build -f

This information comes from the Using the CLI () section of the Garden documentation, which states:

garden build --force  # or -f for short

This command will rebuild all

Build

actions, forcing a rebuild regardless of the existing cache. If you want to rebuild a specific

Build

action, you can specify its name after the command:

garden build my-build --force

By using the

--force

flag, you ensure that Garden performs a fresh build without relying on any previously cached layers or build artifacts. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Thank you for bringing this to my attention. You are correct, and I apologize for the confusion in my previous answer. Let me provide a more accurate explanation based on the available information. You're right that the

--force

flag doesn't actually ignore the container cache. It primarily causes Garden to run all build actions, even if their dependencies haven't changed. To address your specific concern about ignoring the container cache, I've reviewed the provided knowledge sources, and I don't find explicit information about a flag or option that directly ignores the container cache for builds. However, I can provide some relevant information about caching in Garden: 1. For Kubernetes providers, Garden uses a feature called ClusterBuildkit, which has cache configuration options. The default behavior is to use a registry cache, as described in the Kubernetes provider documentation (). 2. If you want to disable caches completely for ClusterBuildkit, you can use the following configuration:

yaml
   clusterBuildkit:
     cache: []

This is mentioned in the same documentation. 3. There's an open issue in the Garden GitHub repository that discusses a related problem with the

--force-build

flag in Garden 0.13 (Bonsai). The issue suggests that the behavior of force building might have changed between versions. GitHub Issue #4800 () Given this information, it appears that there isn't a straightforward command-line option to ignore the container cache specifically. The caching behavior seems to be more deeply integrated into the build process, especially when using Kubernetes providers.

If you need to ensure a completely fresh build without any caching, you might need to look into adjusting the cache configuration in your Garden project settings or consider using provider-specific options. I apologize that I don't have a more direct solution to your specific need. If this is a critical requirement for your workflow, you might want to consider raising this as a feature request on the Garden GitHub repository. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted