Merge pull request #25392 from dvdksn/includes-cleanup

Remove unused includes and fail the build on broken include references

content/includes/aci-ecs-eol.md

@@ -1,3 +0,0 @@
-> [!IMPORTANT]
->
-> Docker Compose's integration for ECS and ACI is retiring in November 2023.

content/includes/buildx-v0.10-disclaimer.md

@@ -1,8 +0,0 @@
-> [!NOTE]
->
-> Buildx v0.10 enables support for a minimal [SLSA Provenance](https://slsa.dev/provenance/)
-> attestation, which requires support for [OCI-compliant](https://github.com/opencontainers/image-spec)
-> multi-platform images. This may introduce issues with registry and runtime support
-> (e.g. [Google Cloud Run and AWS Lambda](https://github.com/docker/buildx/issues/1533)).
-> You can optionally disable the default provenance attestation functionality
-> using `--provenance=false`.

content/includes/compose-eol.md

@@ -1,5 +0,0 @@
-> [!IMPORTANT]
->
-> Docker's documentation refers to and describes Compose V2 functionality. 
->
-> Effective July 2023, Compose V1 stopped receiving updates and is no longer in new Docker Desktop releases. Compose V2 has replaced it and is now integrated into all current Docker Desktop versions.

content/includes/deploy.md

@@ -1,28 +0,0 @@
-Now that we have configured a CI/CD pipeline, let's look at how we can deploy the application. Docker supports deploying containers on Azure ACI and AWS ECS. You can also deploy your application to Kubernetes if you have enabled Kubernetes in Docker Desktop.
-
-## Docker and Azure ACI
-
-The Docker Azure Integration enables developers to use native Docker commands to run applications in Azure Container Instances (ACI) when building cloud-native applications. The new experience provides a tight integration between Docker Desktop and Microsoft Azure allowing developers to quickly run applications using the Docker CLI or VS Code extension to switch seamlessly from local development to cloud deployment.
-
-For detailed instructions, see [Deploying Docker containers on Azure](/cloud/aci-integration/).
-
-## Docker and AWS ECS
-
-The Docker ECS Integration enables developers to use native Docker commands in the Docker Compose CLI to run applications in an Amazon EC2 Container Service (ECS) when building cloud-native applications.
-
-The integration between Docker and Amazon ECS allows developers to use the Docker Compose CLI to set up an AWS context in one Docker command, allowing them to switch from a local context to a cloud context and run applications quickly and easily to simplify multi-container application development on Amazon ECS using Compose files.
-
-For detailed instructions, see [Deploying Docker containers on ECS](/cloud/ecs-integration/).
-
-## Kubernetes
-
-Docker Desktop includes a standalone Kubernetes server and client, as well as Docker CLI integration that runs on your machine. When you enable Kubernetes, you can test your workloads on Kubernetes.
-
-To enable Kubernetes:
-
-1. From the Docker menu, select **Settings**.
-2. Select **Kubernetes** and click **Enable Kubernetes**.
-
-    This starts a Kubernetes single-node cluster when Docker Desktop starts.
-
-For detailed information, see [Deploy on Kubernetes](/manuals/desktop/use-desktop/kubernetes.md) and [Describing apps using Kubernetes YAML](/guides/deployment-orchestration/kube-deploy/#describing-apps-using-kubernetes-yaml).

content/includes/dev-envs-changing.md

@@ -1,5 +0,0 @@
-> [!IMPORTANT]
->
-> Dev Environments is no longer under active development. 
->
-> While the current functionality remains available, it may take us longer to respond to support requests.

content/includes/dockerfile-labs-channel.md

@@ -1,3 +0,0 @@
-> [!IMPORTANT]
->
-> The labs channel gives you access to experimental Dockerfile features not yet available in the stable channel.

content/includes/experimental.md

@@ -1,7 +0,0 @@
-Experimental features provide early access to future product functionality.
-These features are intended for testing and feedback only as they may change
-between releases without warning or can be removed entirely from a future
-release. Experimental features must not be used in production environments.
-Docker does not offer support for experimental features.
-
-For a list of current experimental features in the Docker CLI, see [Docker CLI Experimental features](https://github.com/docker/cli/blob/master/experimental/README.md).

content/includes/guides-get-docker.md

@@ -1 +0,0 @@
-Before you start, get the latest version of [Docker Desktop](/get-started/get-docker.md). Docker adds new features regularly and some parts of this guide may work only with the latest version of Docker Desktop.

content/includes/open-terminal.md

@@ -1,10 +0,0 @@
-> [!TIP]
->
-> To run Docker commands, you must use a terminal. Based on your
-> operating system, you can open a terminal by doing the following:
->
-> For Windows, select the Start Menu, specify `cmd`, and then select
-> **Command Prompt**.
->
-> For Mac, select the **Launchpad** icon in the Dock, specify `Terminal` in the
-> search field, then select **Terminal**.

content/manuals/scout/integrations/environment/cli.md

@@ -5,8 +5,6 @@ title: Generic environment integration with CLI
 linkTitle: Generic (CLI)
 ---
 
-{{% include "scout-early-access.md" %}}
-
 You can create a generic environment integration by running the Docker Scout
 CLI client in your CI workflows. The CLI client is available as a binary on
 GitHub and as a container image on Docker Hub. Use the client to invoke the

content/manuals/scout/integrations/environment/sysdig.md

@@ -5,8 +5,6 @@ description: Integrate your runtime environments with Docker Scout using Sysdig
 keywords: scout, sysdig, integration, image analysis, environments, supply chain
 ---
 
-{{% include "scout-early-access.md" %}}
-
 The Sysdig integration enables Docker Scout to automatically detect the images
 you're using for your running workloads. Activating this integration gives you
 real-time insights about your security posture, and lets you compare your

content/reference/compose-file/develop.md

@@ -11,7 +11,7 @@ weight: 150
 >
 > Develop is an optional part of the Compose Specification. It is available with Docker Compose version 2.22.0 and later.
 
-{{% include "compose/develop.md" %}}
+{{% include "compose/services-develop.md" %}}
 
 This page defines how Compose behaves to efficiently assist you and defines the development constraints and workflows set by Compose. Only a subset of Compose file services may require a `develop` subsection.
 

layouts/_shortcodes/include.html

@@ -1,3 +1,17 @@
+{{/*
+  include shortcode — inlines a reusable snippet from content/includes.
+
+  Usage:
+    {{% include "root-errors.md" %}}
+    {{% include "compose/services.md" %}}
+
+  The argument is a path relative to content/includes. The build fails with
+  a clear message if the target does not exist, so a renamed or deleted
+  snippet surfaces immediately instead of silently rendering nothing.
+*/}}
 {{ $fileToInclude := .Get 0 }}
 {{ $filePath := printf "includes/%s" $fileToInclude }}
-{{ readFile $filePath | safeHTML }}
+{{ if not (fileExists $filePath) }}
+  {{- errorf "include shortcode: file %q not found: %s" $filePath .Position -}}
+{{ end }}
+{{ readFile $filePath | safeHTML }}