docs: change cache storage links to exporter to docs site

Temporary fix while we update docs upstream.

Co-Authored-By: David Karlsson <david.karlsson@docker.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>

docs/guides/cache/index.md

@@ -127,10 +127,10 @@ with both parameters to find the results that work best for you.
 
 ### Cache compression
 
-<!-- FIXME: this link won't work on docs.docker.com -->
+<!-- TODO: change this link to a local link -->
 
 The cache compression options are the same as the
-[exporter compression options](../exporters/index.md#compression).
+[exporter compression options](https://docs.docker.com/build/building/exporters/#compression).
 
 For example, to compress the `registry` cache with `zstd` compression:
 
@@ -142,10 +142,10 @@ $ docker buildx build --push -t <registry>/<image> \
 
 ### OCI media types
 
-<!-- FIXME: this link won't work on docs.docker.com -->
+<!-- TODO: change this link to a local link -->
 
 The cache OCI options are the same as the
-[exporter OCI options](../exporters/index.md#oci-media-types).
+[exporter OCI options](https://docs.docker.com/build/building/exporters/#oci-media-types).
 
 For example, to export OCI media type cache, use the `oci-mediatypes` property:
 

docs/guides/cicd.md

@@ -40,7 +40,7 @@ jobs:
 In this example we are also using 3 other actions:
 
 * [`setup-buildx`](https://github.com/docker/setup-buildx-action) action will create and boot a builder using by
-default the `docker-container` [builder driver](../reference/buildx_create.md#driver).
+default the `docker-container` [builder driver](https://docs.docker.com/engine/reference/commandline/buildx_create/#driver).
 This is **not required but recommended** using it to be able to build multi-platform images, export cache, etc.
 * [`setup-qemu`](https://github.com/docker/setup-qemu-action) action can be useful if you want
 to add emulation support with QEMU to be able to build against more platforms.

docs/guides/exporters/image-registry.md

@@ -37,7 +37,7 @@ The following table describes the available parameters that you can pass to
 | `store`                | `true`,`false`                         | `true`  | Store the result images to the worker's (for example, containerd) image store, and ensures that the image has all blobs in the content store. Ignored if the worker doesn't have image store (when using OCI workers, for example). |
 | `annotation.<key>`     | String                                 |         | Attach an annotation with the respective `key` and `value` to the built image,see [annotations][4]                                                                                                                                  |
 
-[1]: index.md#cache-compression
+[1]: index.md#compression
 [2]: index.md#oci-media-types
 [3]: index.md#build-info
 [4]: #annotations

docs/guides/exporters/index.md

@@ -2,8 +2,8 @@
 
 Exporters save your build results to a specified output type. You specify the
 exporter to use with the
-[`--output` CLI option](../../reference/buildx_build.md#output). Buildx supports
-the following exporters:
+[`--output` CLI option](https://docs.docker.com/engine/reference/commandline/buildx_build/#output).
+Buildx supports the following exporters:
 
 - `image`: exports the build result to a container image.
 - `registry`: exports the build result into a container image, and pushes it to

docs/guides/exporters/oci-docker.md

@@ -35,7 +35,7 @@ The following table describes the available parameters:
 | `buildinfo-attrs`   | `true`,`false`                         | `false` | Attach inline [build info attributes][3]                                                                                              |
 | `annotation.<key>`  | String                                 |         | Attach an annotation with the respective `key` and `value` to the built image,see [annotations][4]                                    |
 
-[1]: index.md#cache-compression
+[1]: index.md#compression
 [2]: index.md#oci-media-types
 [3]: index.md#build-info
 [4]: #annotations