vendor: github.com/docker/buildx v0.26.0

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: crazy-max

_vendor/github.com/docker/buildx/docs/bake-reference.md

@@ -1,6 +1,6 @@
 # github.com/moby/moby v28.3.2+incompatible
 # github.com/moby/buildkit v0.23.2
-# github.com/docker/buildx v0.25.0
+# github.com/docker/buildx v0.26.0
 # github.com/docker/cli v28.3.3-0.20250711132746-c69d8bde4adc+incompatible
 # github.com/docker/compose/v2 v2.38.2
 # github.com/docker/model-cli v0.1.33-0.20250703103301-d4e4936a9eb2

_vendor/modules.txt

@@ -8,6 +8,7 @@ cname:
     - docker buildx bake
     - docker buildx build
     - docker buildx create
+    - docker buildx dap
     - docker buildx debug
     - docker buildx dial-stdio
     - docker buildx du
@@ -24,6 +25,7 @@ clink:
     - docker_buildx_bake.yaml
     - docker_buildx_build.yaml
     - docker_buildx_create.yaml
+    - docker_buildx_dap.yaml
     - docker_buildx_debug.yaml
     - docker_buildx_dial-stdio.yaml
     - docker_buildx_du.yaml

data/buildx/docker_buildx.yaml

@@ -311,6 +311,11 @@ examples: |-
     The file can be an HCL, JSON or Compose file. If multiple files are specified,
     all are read and the build configurations are combined.
 
+    Alternatively, the environment variable `BUILDX_BAKE_FILE` can be used to specify the build definition to use.
+    This is mutually exclusive with `-f` / `--file`; if both are specified, the environment variable is ignored.
+    Multiple definitions can be specified by separating them with the system's path separator
+    (typically `;` on Windows and `:` elsewhere), but can be changed with `BUILDX_BAKE_PATH_SEPARATOR`.
+
     You can pass the names of the targets to build, to build only specific target(s).
     The following example builds the `db` and `webapp-release` targets that are
     defined in the `docker-bake.dev.hcl` file:
@@ -366,12 +371,15 @@ examples: |-
 
     ```console
     $ docker buildx bake --list=variables
-    VARIABLE      VALUE                DESCRIPTION
-    REGISTRY      docker.io/username   Registry and namespace
-    IMAGE_NAME    my-app               Image name
-    GO_VERSION    <null>
+    VARIABLE      TYPE      VALUE                DESCRIPTION
+    REGISTRY      string    docker.io/username   Registry and namespace
+    IMAGE_NAME    string    my-app               Image name
+    GO_VERSION              <null>
+    DEBUG         bool      false                Add debug symbols
     ```
 
+    Variable types will be shown when set using the `type` property in the Bake file.
+
     By default, the output of `docker buildx bake --list` is presented in a table
     format. Alternatively, you can use a long-form CSV syntax and specify a
     `format` attribute to output the list in JSON.
@@ -531,6 +539,7 @@ examples: |-
     * `context`
     * `dockerfile`
     * `entitlements`
+    * `extra-hosts`
     * `labels`
     * `load`
     * `no-cache`

data/buildx/docker_buildx_bake.yaml

@@ -703,13 +703,15 @@ examples: |-
     Define additional build context with specified contents. In Dockerfile the context can be accessed when `FROM name` or `--from=name` is used.
     When Dockerfile defines a stage with the same name it is overwritten.
 
-    The value can be a local source directory, [local OCI layout compliant directory](https://github.com/opencontainers/image-spec/blob/main/image-layout.md), container image (with docker-image:// prefix), Git or HTTP URL.
+    The value can be a:
 
-    Replace `alpine:latest` with a pinned one:
+    - local source directory
+    - [local OCI layout compliant directory](https://github.com/opencontainers/image-spec/blob/main/image-layout.md)
+    - container image
+    - Git URL
+    - HTTP URL
 
-    ```console
-    $ docker buildx build --build-context alpine=docker-image://alpine@sha256:0123456789 .
-    ```
+    #### Use a local path {#local-path}
 
     Expose a secondary local source directory:
 
@@ -718,6 +720,16 @@ examples: |-
     # docker buildx build --build-context project=https://github.com/myuser/project.git .
     ```
 
+    #### Use a container image {#docker-image}
+
+    Use the `docker-image://` scheme.
+
+    Replace `alpine:latest` with a pinned one:
+
+    ```console
+    $ docker buildx build --build-context alpine=docker-image://alpine@sha256:0123456789 .
+    ```
+
     ```dockerfile
     # syntax=docker/dockerfile:1
     FROM alpine
@@ -726,7 +738,10 @@ examples: |-
 
     #### Use an OCI layout directory as build context {#source-oci-layout}
 
-    Source an image from a local [OCI layout compliant directory](https://github.com/opencontainers/image-spec/blob/main/image-layout.md),
+    Use the `oci-layout:///` scheme.
+
+    Source an image from a local
+    [OCI layout compliant directory](https://github.com/opencontainers/image-spec/blob/main/image-layout.md),
     either by tag, or by digest:
 
     ```console
@@ -744,7 +759,6 @@ examples: |-
     ```
 
     The OCI layout directory must be compliant with the [OCI layout specification](https://github.com/opencontainers/image-spec/blob/main/image-layout.md).
-    You can reference an image in the layout using either tags, or the exact digest.
 
     ### Override the configured builder instance (--builder) {#builder}
 
@@ -756,25 +770,25 @@ examples: |-
     --cache-from=[NAME|type=TYPE[,KEY=VALUE]]
     ```
 
-    Use an external cache source for a build. Supported types are `registry`,
-    `local`, `gha` and `s3`.
+    Use an external cache source for a build. Supported types are:
 
-    - [`registry` source](https://github.com/moby/buildkit#registry-push-image-and-cache-separately)
+    - [`registry`](/build/cache/backends/registry/)
       can import cache from a cache manifest or (special) image configuration on the
       registry.
-    - [`local` source](https://github.com/moby/buildkit#local-directory-1) can
+    - [`local`](/build/cache/backends/local/) can
       import cache from local files previously exported with `--cache-to`.
-    - [`gha` source](https://github.com/moby/buildkit#github-actions-cache-experimental)
+    - [`gha`](/build/cache/backends/gha/)
+      can import cache from a previously exported cache with `--cache-to` in your
+      GitHub repository.
+    - [`s3`](/build/cache/backends/s3/)
       can import cache from a previously exported cache with `--cache-to` in your
-      GitHub repository
-    - [`s3` source](https://github.com/moby/buildkit#s3-cache-experimental)
+      S3 bucket.
+    - [`azblob`](/build/cache/backends/azblob/)
       can import cache from a previously exported cache with `--cache-to` in your
-      S3 bucket
+      Azure bucket.
 
     If no type is specified, `registry` exporter is used with a specified reference.
 
-    `docker` driver currently only supports importing build cache from the registry.
-
     ```console
     $ docker buildx build --cache-from=user/app:cache .
     $ docker buildx build --cache-from=user/app .
@@ -784,7 +798,43 @@ examples: |-
     $ docker buildx build --cache-from=type=s3,region=eu-west-1,bucket=mybucket .
     ```
 
-    More info about cache exporters and available attributes: https://github.com/moby/buildkit#export-cache
+    > [!NOTE]
+    > More info about cache exporters and available attributes can be found in the
+    > [Cache storage backends documentation](/build/cache/backends/)
+
+    ### Export build cache to an external cache destination (--cache-to) {#cache-to}
+
+    ```text
+    --cache-to=[NAME|type=TYPE[,KEY=VALUE]]
+    ```
+
+    Export build cache to an external cache destination. Supported types are:
+
+    - [`registry`](/build/cache/backends/registry/) exports
+      build cache to a cache manifest in the registry.
+    - [`local`](/build/cache/backends/local/) exports
+      cache to a local directory on the client.
+    - [`inline`](/build/cache/backends/inline/) writes the
+      cache metadata into the image configuration.
+    - [`gha`](/build/cache/backends/gha/) exports cache
+      through the GitHub Actions Cache service API.
+    - [`s3`](/build/cache/backends/s3/) exports cache to a
+      S3 bucket.
+    - [`azblob`](/build/cache/backends/azblob/) exports
+      cache to an Azure bucket.
+
+    ```console
+    $ docker buildx build --cache-to=user/app:cache .
+    $ docker buildx build --cache-to=type=inline .
+    $ docker buildx build --cache-to=type=registry,ref=user/app .
+    $ docker buildx build --cache-to=type=local,dest=path/to/cache .
+    $ docker buildx build --cache-to=type=gha .
+    $ docker buildx build --cache-to=type=s3,region=eu-west-1,bucket=mybucket .
+    ```
+
+    > [!NOTE]
+    > More info about cache exporters and available attributes can be found in the
+    > [Cache storage backends documentation](/build/cache/backends/)
 
     ### Invoke a frontend method (--call) {#call}
 
@@ -947,45 +997,6 @@ examples: |-
     release (default) is an empty scratch image with only compiled assets
     ```
 
-    ### Export build cache to an external cache destination (--cache-to) {#cache-to}
-
-    ```text
-    --cache-to=[NAME|type=TYPE[,KEY=VALUE]]
-    ```
-
-    Export build cache to an external cache destination. Supported types are
-    `registry`, `local`, `inline`, `gha` and `s3`.
-
-    - [`registry` type](https://github.com/moby/buildkit#registry-push-image-and-cache-separately) exports build cache to a cache manifest in the registry.
-    - [`local` type](https://github.com/moby/buildkit#local-directory-1) exports
-      cache to a local directory on the client.
-    - [`inline` type](https://github.com/moby/buildkit#inline-push-image-and-cache-together)
-      writes the cache metadata into the image configuration.
-    - [`gha` type](https://github.com/moby/buildkit#github-actions-cache-experimental)
-      exports cache through the [GitHub Actions Cache service API](https://github.com/tonistiigi/go-actions-cache/blob/master/api.md#authentication).
-    - [`s3` type](https://github.com/moby/buildkit#s3-cache-experimental) exports
-      cache to a S3 bucket.
-
-    The `docker` driver only supports cache exports using the `inline` and `local`
-    cache backends.
-
-    Attribute key:
-
-    - `mode` - Specifies how many layers are exported with the cache. `min` on only
-      exports layers already in the final build stage, `max` exports layers for
-      all stages. Metadata is always exported for the whole build.
-
-    ```console
-    $ docker buildx build --cache-to=user/app:cache .
-    $ docker buildx build --cache-to=type=inline .
-    $ docker buildx build --cache-to=type=registry,ref=user/app .
-    $ docker buildx build --cache-to=type=local,dest=path/to/cache .
-    $ docker buildx build --cache-to=type=gha .
-    $ docker buildx build --cache-to=type=s3,region=eu-west-1,bucket=mybucket .
-    ```
-
-    More info about cache exporters and available attributes: https://github.com/moby/buildkit#export-cache
-
     ### Use a custom parent cgroup (--cgroup-parent) {#cgroup-parent}
 
     When you run `docker buildx build` with the `--cgroup-parent` option,

data/buildx/docker_buildx_build.yaml

@@ -0,0 +1,37 @@
+command: docker buildx dap
+short: Start debug adapter protocol compatible debugger
+long: Start debug adapter protocol compatible debugger
+pname: docker buildx
+plink: docker_buildx.yaml
+cname:
+    - docker buildx dap build
+clink:
+    - docker_buildx_dap_build.yaml
+inherited_options:
+    - option: builder
+      value_type: string
+      description: Override the configured builder instance
+      deprecated: false
+      hidden: false
+      experimental: false
+      experimentalcli: false
+      kubernetes: false
+      swarm: false
+    - option: debug
+      shorthand: D
+      value_type: bool
+      default_value: "false"
+      description: Enable debug logging
+      deprecated: false
+      hidden: false
+      experimental: false
+      experimentalcli: false
+      kubernetes: false
+      swarm: false
+deprecated: false
+hidden: false
+experimental: false
+experimentalcli: true
+kubernetes: false
+swarm: false
+

data/buildx/docker_buildx_dap.yaml

@@ -0,0 +1,34 @@
+command: docker buildx dap attach
+short: Attach to a container created by the dap evaluate request
+long: Attach to a container created by the dap evaluate request
+usage: docker buildx dap attach PATH
+pname: docker buildx dap
+plink: docker_buildx_dap.yaml
+inherited_options:
+    - option: builder
+      value_type: string
+      description: Override the configured builder instance
+      deprecated: false
+      hidden: false
+      experimental: false
+      experimentalcli: false
+      kubernetes: false
+      swarm: false
+    - option: debug
+      shorthand: D
+      value_type: bool
+      default_value: "false"
+      description: Enable debug logging
+      deprecated: false
+      hidden: false
+      experimental: false
+      experimentalcli: false
+      kubernetes: false
+      swarm: false
+deprecated: false
+hidden: true
+experimental: false
+experimentalcli: true
+kubernetes: false
+swarm: false
+