diff --git a/docs/guides/bake/build-contexts.md b/docs/guides/bake/build-contexts.md index e6ece739..21a52e71 100644 --- a/docs/guides/bake/build-contexts.md +++ b/docs/guides/bake/build-contexts.md @@ -1,7 +1,4 @@ ---- -title: "Defining additional build contexts and linking targets" -keywords: build, buildx, bake, buildkit, hcl ---- +# Defining additional build contexts and linking targets In addition to the main `context` key that defines the build context each target can also define additional named contexts with a map defined with key `contexts`. diff --git a/docs/guides/bake/compose-file.md b/docs/guides/bake/compose-file.md index e4cb7db4..5086de6c 100644 --- a/docs/guides/bake/compose-file.md +++ b/docs/guides/bake/compose-file.md @@ -1,7 +1,4 @@ ---- -title: "Building from Compose file" -keywords: build, buildx, bake, buildkit, compose ---- +# Building from Compose file ## Specification diff --git a/docs/guides/bake/configuring-build.md b/docs/guides/bake/configuring-build.md index 66149726..fe6535da 100644 --- a/docs/guides/bake/configuring-build.md +++ b/docs/guides/bake/configuring-build.md @@ -1,7 +1,4 @@ ---- -title: "Configuring builds" -keywords: build, buildx, bake, buildkit, hcl, json ---- +# Configuring builds Bake supports loading build definition from files, but sometimes you need even more flexibility to configure this definition. diff --git a/docs/guides/bake/file-definition.md b/docs/guides/bake/file-definition.md index 3166706f..5714d711 100644 --- a/docs/guides/bake/file-definition.md +++ b/docs/guides/bake/file-definition.md @@ -1,7 +1,4 @@ ---- -title: "Bake file definition" -keywords: build, buildx, bake, buildkit, hcl, json, compose ---- +# Bake file definition `buildx bake` supports HCL, JSON and Compose file format for defining build [groups](#group), [targets](#target) as well as [variables](#variable) and diff --git a/docs/guides/bake/hcl-funcs.md b/docs/guides/bake/hcl-funcs.md index 56196f80..6019e79d 100644 --- a/docs/guides/bake/hcl-funcs.md +++ b/docs/guides/bake/hcl-funcs.md @@ -1,7 +1,4 @@ ---- -title: "User defined HCL functions" -keywords: build, buildx, bake, buildkit, hcl ---- +# User defined HCL functions ## Using interpolation to tag an image with the git sha diff --git a/docs/guides/bake/index.md b/docs/guides/bake/index.md index 2ae4ccf7..e8ad3a89 100644 --- a/docs/guides/bake/index.md +++ b/docs/guides/bake/index.md @@ -1,7 +1,4 @@ ---- -title: "High-level build options with Bake" -keywords: build, buildx, bake, buildkit, hcl, json, compose ---- +# High-level build options with Bake > This command is experimental. > diff --git a/docs/guides/cni-networking.md b/docs/guides/cni-networking.md index fe488280..2af87897 100644 --- a/docs/guides/cni-networking.md +++ b/docs/guides/cni-networking.md @@ -1,8 +1,4 @@ ---- -title: "CNI networking" -description: "Enhance your builder with CNI networking" -keywords: build, buildx, buildkit, cni, network ---- +# CNI networking It can be useful to use a bridge network for your builder if for example you encounter a network port contention during multiple builds. If you're using diff --git a/docs/guides/color-output.md b/docs/guides/color-output.md index aa859cec..22a25e08 100644 --- a/docs/guides/color-output.md +++ b/docs/guides/color-output.md @@ -1,8 +1,4 @@ ---- -title: "Color output controls" -description: "Modifying colors of progress output" -keywords: build, buildx, buildkit ---- +# Color output controls Buildx has support for modifying the colors that are used to output information to the terminal. You can set the environment variable `BUILDKIT_COLORS` to diff --git a/docs/guides/custom-network.md b/docs/guides/custom-network.md index 249cc24d..c1dd2155 100644 --- a/docs/guides/custom-network.md +++ b/docs/guides/custom-network.md @@ -1,8 +1,4 @@ ---- -title: "Using a custom network" -description: "Create and use a custom network for your build" -keywords: build, buildx, buildkit, network ---- +# Using a custom network [Create a network](https://docs.docker.com/engine/reference/commandline/network_create/) named `foonet`: diff --git a/docs/guides/custom-registry-config.md b/docs/guides/custom-registry-config.md index 7f6630dd..7aa1381b 100644 --- a/docs/guides/custom-registry-config.md +++ b/docs/guides/custom-registry-config.md @@ -1,8 +1,4 @@ ---- -title: "Using a custom registry configuration" -description: "Set registry configuration in your builder" -keywords: build, buildx, buildkit, registry ---- +# Using a custom registry configuration If you [create a `docker-container` or `kubernetes` builder](https://docs.docker.com/engine/reference/commandline/buildx_create/) and have specified certificates for registries in the [BuildKit daemon configuration](https://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md), diff --git a/docs/guides/kubernetes-builder.md b/docs/guides/kubernetes-builder.md index c0a4dc17..aa856be2 100644 --- a/docs/guides/kubernetes-builder.md +++ b/docs/guides/kubernetes-builder.md @@ -1,8 +1,4 @@ ---- -title: "Kubernetes builder" -description: "Connect buildx to a kubernetes cluster" -keywords: build, buildx, buildkit ---- +# Kubernetes builder The buildx kubernetes driver allows connecting your local development or ci environments to your kubernetes cluster to allow access to more powerful diff --git a/docs/guides/opentelemetry.md b/docs/guides/opentelemetry.md index 11a45e72..aca59786 100644 --- a/docs/guides/opentelemetry.md +++ b/docs/guides/opentelemetry.md @@ -1,8 +1,4 @@ ---- -title: "OpenTelemetry support" -description: "OpenTelemetry support for your builder" -keywords: build, buildx, buildkit, opentelemetry, tracing ---- +# OpenTelemetry support To capture the trace to [Jaeger](https://github.com/jaegertracing/jaeger), set `JAEGER_TRACE` environment variable to the collection address using a `driver-opt`. diff --git a/docs/guides/registry-mirror.md b/docs/guides/registry-mirror.md index 0218a9fb..f22198b6 100644 --- a/docs/guides/registry-mirror.md +++ b/docs/guides/registry-mirror.md @@ -1,8 +1,4 @@ ---- -title: "Registry mirror" -description: "Using a registry mirror in your build" -keywords: build, buildx, buildkit, registry ---- +# Registry mirror You can define a registry mirror to use for your builds by providing a [BuildKit daemon configuration](https://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md) while creating a builder with the [`--config` flags](https://docs.docker.com/engine/reference/commandline/buildx_create/#config). diff --git a/docs/guides/remote-builder.md b/docs/guides/remote-builder.md index 837fe21d..7caf5825 100644 --- a/docs/guides/remote-builder.md +++ b/docs/guides/remote-builder.md @@ -1,8 +1,4 @@ ---- -title: "Remote builder" -description: "Connect buildx to an external buildkitd instance" -keywords: build, buildx, buildkit ---- +# Remote builder The buildx remote driver allows for more complex custom build workloads that allow users to connect to external buildkit instances. This is useful for diff --git a/docs/guides/resource-limiting.md b/docs/guides/resource-limiting.md index 4afaa845..51c1c6e0 100644 --- a/docs/guides/resource-limiting.md +++ b/docs/guides/resource-limiting.md @@ -1,8 +1,4 @@ ---- -title: "Resource limiting" -description: "Max parallelism and limit on TCP connection in your build" -keywords: build, buildx, buildkit, compute, network ---- +# Resource limiting ## Max parallelism