provenance note

content/overview/faq.mdx

@@ -29,3 +29,13 @@ Yes! Check out our [integration guide](guides/arm-containers#what-about-multi-ar
 ### Can I use Depot with my existing `docker build` or `docker buildx build` commands?
 
 Yes! We have a [`depot configure-docker`](/docs/cli/reference#depot-configure-docker) command that configures Depot as a plugin for the Docker CLI and sets Depot as the default builder for both `docker build` and `docker buildx build`. See our [`docker build` guide](/docs/guides/docker-build) for more details.
+
+### What are these extra files in my registry?
+
+Registries like Amazon Elastic Container Registry (ECR) and Google Container Registry (GCR) don't accurately display provenance information for a given image. Provenance is a set of metadata that describes how an image was built. This metadata is stored in the registry alongside the image. It's enabled by default in `docker build` and thus by default in `depot build` as well.
+
+If you would like to clean up the clutter, you can run your build with `--provenance=false`:
+
+```shell
+depot build -t <your-registry> --push --provenance=false .
+```