docker · sarahsanders-docker · Jan 21, 2025 · Dec 18, 2024 · Dec 18, 2024 · Dec 18, 2024
diff --git a/content/manuals/admin/company/_index.md b/content/manuals/admin/company/_index.md
@@ -42,6 +42,8 @@ aliases:
 - /docker-hub/creating-companies/
 ---
 
+{{< summary-bar feature_name="Company" >}}
+
 {{< include "admin-company-overview.md" >}}
 
 Learn how to administer a company in the following sections.

diff --git a/content/manuals/admin/company/new-company.md b/content/manuals/admin/company/new-company.md
@@ -6,6 +6,8 @@ aliases:
 - /docker-hub/new-company/
 ---
 
+{{< summary-bar feature_name="Company" >}}
+
 You can create a new company in the Docker Admin Console. Before you begin, you must:
 - Be the owner of the organization you want to add to your company
 - Have a Docker Business subscription

diff --git a/content/manuals/admin/company/organizations.md b/content/manuals/admin/company/organizations.md
@@ -4,6 +4,8 @@ keywords: company, multiple organizations, manage organizations
 title: Manage company organizations
 ---
 
+{{< summary-bar feature_name="Company" >}}
+
 You can manage the organizations in a company in the Docker Admin Console.
 
 {{< include "admin-early-access.md" >}}

diff --git a/content/manuals/admin/company/owners.md b/content/manuals/admin/company/owners.md
@@ -6,6 +6,8 @@ aliases:
 - /docker-hub/company-owner/
 ---
 
+{{< summary-bar feature_name="Company" >}}
+
 A company can have multiple owners. Company owners have company-wide
 observability and can manage company-wide settings that apply to all associated
 organizations. In addition, company owners have the same access as organization

diff --git a/content/manuals/admin/company/users.md b/content/manuals/admin/company/users.md
@@ -4,6 +4,8 @@ keywords: company, company users, users, admin, Admin Console
 title: Manage company users
 ---
 
+{{< summary-bar feature_name="Company" >}}
+
 You can manage users at the company-level in the Docker Admin Console.
 
 {{% admin-users product="admin" layer="company" %}}

diff --git a/content/manuals/admin/organization/activity-logs.md b/content/manuals/admin/organization/activity-logs.md
@@ -7,6 +7,8 @@ aliases:
 - /docker-hub/audit-log/
 ---
 
+{{< summary-bar feature_name="Activity logs" >}}
+
 Activity logs display a chronological list of activities that occur at organization and repository levels. It provides a report to owners on all their member activities.
 
 With activity logs, owners can view and track:
@@ -18,10 +20,6 @@ For example, activity logs display activities such as the date when a repository
 
 Owners can also see the activity logs for their repository if the repository is part of the organization subscribed to a Docker Business or Team plan.
 
-> [!NOTE]
->
-> Activity logs requires a [Docker Team or Business subscription](/manuals/subscription/_index.md).
-
 ## Manage activity logs
 
 {{< tabs >}}

diff --git a/content/manuals/admin/organization/insights.md b/content/manuals/admin/organization/insights.md
@@ -4,9 +4,7 @@ keywords: organization, insights
 title: Insights
 ---
 
-> [!NOTE]
->
-> Insights requires a [Docker Business subscription](../../subscription/details.md#docker-business) and administrators must [enforce sign-in](/security/for-admins/enforce-sign-in/). This ensures users sign in with an account associated with their organization.
+{{< summary-bar feature_name="Insights" >}}
 
 Insights helps administrators visualize and understand how Docker is used within
 their organizations. With Insights, administrators can ensure their teams are
@@ -24,6 +22,12 @@ Key benefits include:
 - Optimized license use. Ensure that developers have access to advanced
   features provided by a Docker subscription.
 
+## Prerequisites
+
+- [Docker Business subscription](../../subscription/details.md#docker-business)
+- Administrators must [enforce sign-in](/security/for-admins/enforce-sign-in/) for users
+- Insights enabled by your Customer Success Manager
+
 ## View Insights for organization users
 
 {{< include "admin-early-access.md" >}}

@@ -6,12 +6,7 @@ aliases:
   - /build/customize/bake/
 ---
 
-{{% experimental %}}
-
-Bake is an experimental feature, and we are looking for
-[feedback from users](https://github.com/docker/buildx/issues).
-
-{{% /experimental %}}
+{{< summary-bar feature_name="Build bake" >}}
 
 Bake is a feature of Docker Buildx that lets you define your build configuration
 using a declarative file, as opposed to specifying a complex CLI expression. It

@@ -6,10 +6,7 @@ aliases:
   - /build/building/cache/backends/azblob/
 ---
 
-{{% experimental %}}
-This is an experimental feature. The interface and behavior are unstable and
-may change in future releases.
-{{% /experimental %}}
+{{< summary-bar feature_name="Azure blob" >}}
 
 The `azblob` cache store uploads your resulting build cache to
 [Azure's blob storage service](https://azure.microsoft.com/en-us/services/storage/blobs/).

@@ -6,10 +6,7 @@ aliases:
   - /build/building/cache/backends/gha/
 ---
 
-{{% restricted %}}
-This is an experimental feature. The interface and behavior are unstable and
-may change in future releases.
-{{% /restricted %}}
+{{< summary-bar feature_name="GitHub Actions cache" >}}
 
 The GitHub Actions cache utilizes the
 [GitHub-provided Action's cache](https://github.com/actions/cache) or other

@@ -6,10 +6,7 @@ aliases:
   - /build/building/cache/backends/s3/
 ---
 
-{{% restricted %}}
-This is an experimental feature. The interface and behavior are unstable and
-may change in future releases.
-{{% /restricted %}}
+{{< summary-bar feature_name="Amazon S3 cache" >}}
 
 The `s3` cache storage uploads your resulting build cache to
 [Amazon S3 file storage service](https://aws.amazon.com/s3/)

@@ -11,7 +11,7 @@ description: Learn how to use build checks to validate your build configuration.
 keywords: build, buildx, buildkit, checks, validate, configuration, lint
 ---
 
-{{< introduced buildx 0.15.0 >}}
+{{< summary-bar feature_name="Build checks" >}}
 
 Build checks are a feature introduced in Dockerfile 1.8. It lets you validate
 your build configuration and conduct a series of checks prior to executing your

@@ -31,11 +31,7 @@ message that caused the build to fail:
 
 ## Import build records to Docker Desktop
 
-{{< introduced desktop 4.31 >}}
-
-{{% experimental title="Beta feature" %}}
-Import builds is currently in [Beta](../../../release-lifecycle.md#Beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="Import builds" >}}
 
 The job summary includes a link for downloading a build record archive for the
 run. The build record archive is a ZIP file containing the details about a build

@@ -84,11 +84,7 @@ jobs:
 
 ### Cache backend API
 
-{{% experimental %}}
-This cache exporter is experimental. Please provide feedback on the
-[BuildKit repository](https://github.com/moby/buildkit)
-if you experience any issues.
-{{% /experimental %}}
+{{< summary-bar feature_name="Cache backend API" >}}
 
 The [GitHub Actions cache exporter](../../cache/backends/gha.md)
 backend uses the [GitHub Cache API](https://github.com/tonistiigi/go-actions-cache/blob/master/api.md)

@@ -6,7 +6,7 @@ linkTitle: Compose Bridge
 weight: 50
 ---
 
-{{< include "compose-bridge-experimental.md" >}}
+{{< summary-bar feature_name="Compose bridge" >}}
 
 Compose Bridge lets you transform your Compose configuration file into configuration files for different platforms, primarily focusing on Kubernetes. The default transformation generates Kubernetes manifests and a Kustomize overlay which are designed for deployment on Docker Desktop with Kubernetes enabled.  
 

@@ -6,7 +6,7 @@ description: Learn about how Compose Bridge can function a kubectl plugin
 keywords: kubernetes, compose, compose bridge, plugin, advanced
 ---
 
-{{< include "compose-bridge-experimental.md" >}}
+{{< summary-bar feature_name="Compose bridge" >}}
 
 Compose Bridge can also function as a `kubectl` plugin, allowing you to integrate its capabilities directly into your Kubernetes command-line operations. This integration simplifies the process of converting and deploying applications from Docker Compose to Kubernetes.
 

@@ -6,7 +6,7 @@ description: Learn about the Compose Bridge templates syntax
 keywords: compose, bridge, templates
 ---
 
-{{< include "compose-bridge-experimental.md" >}}
+{{< summary-bar feature_name="Compose bridge" >}}
 
 This page explains how Compose Bridge utilizes templating to efficiently translate Docker Compose files into Kubernetes manifests. It also explain how you can customize these templates for your specific requirements and needs, or how you can build your own transformation. 
 

@@ -6,7 +6,7 @@ description: Learn about and use the Compose Bridge default transformation
 keywords: compose, bridge, kubernetes
 ---
 
-{{< include "compose-bridge-experimental.md" >}}
+{{< summary-bar feature_name="Compose bridge" >}}
 
 Compose Bridge supplies an out-of-the box transformation for your Compose configuration file. Based on an arbitrary `compose.yaml` file, Compose Bridge produces:
 

diff --git a/content/manuals/copilot/_index.md b/content/manuals/copilot/_index.md
@@ -15,9 +15,7 @@ description: |
 keywords: Docker, GitHub Copilot, extension, Visual Studio Code, chat, ai, containerization
 ---
 
-{{% restricted title="Early Access" %}}
-The Docker for GitHub Copilot extension is an [early access](/release-lifecycle#early-access-ea) product.
-{{% /restricted %}}
+{{< summary-bar feature_name="Docker GitHub Copilot" >}}
 
 The [Docker for GitHub Copilot](https://github.com/marketplace/docker-for-github-copilot)
 extension integrates Docker's capabilities with GitHub Copilot, providing

diff --git a/content/manuals/copilot/examples.md b/content/manuals/copilot/examples.md
@@ -7,9 +7,7 @@ description: |
 weight: 30
 ---
 
-{{% restricted title="Early Access" %}}
-The Docker for GitHub Copilot extension is an [early access](/release-lifecycle#early-access-ea) product.
-{{% /restricted %}}
+{{< summary-bar feature_name="Docker GitHub Copilot" >}}
 
 ## Use cases
 

diff --git a/content/manuals/copilot/install.md b/content/manuals/copilot/install.md
@@ -7,9 +7,7 @@ description: |
 weight: 10
 ---
 
-{{% restricted title="Early Access" %}}
-The Docker for GitHub Copilot extension is an [early access](/release-lifecycle#early-access-ea) product.
-{{% /restricted %}}
+{{< summary-bar feature_name="Docker GitHub Copilot" >}}
 
 To use the Docker for GitHub copilot extension, you first need to
 [install](#install) the extension for your organization, and

diff --git a/content/manuals/copilot/usage.md b/content/manuals/copilot/usage.md
@@ -8,9 +8,7 @@ description: |
 weight: 20
 ---
 
-{{% restricted title="Early Access" %}}
-The Docker for GitHub Copilot extension is an [early access](/release-lifecycle#early-access-ea) product.
-{{% /restricted %}}
+{{< summary-bar feature_name="Docker GitHub Copilot" >}}
 
 The Docker Extension for GitHub Copilot provides a chat interface that you can
 use to interact with the Docker agent. You can ask questions and get help

@@ -11,9 +11,7 @@ params:
       text: New
 ---
 
-{{% experimental title="Beta" %}}
-Docker Desktop CLI is currently in [Beta](../../release-lifecycle.md#beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="Docker Desktop CLI" >}}
 
 The Docker Desktop CLI lets you perform key operations such as starting, stopping, restarting, and checking the status of Docker Desktop directly from the command line. It is available with Docker Desktop version 4.37 and later.
 

@@ -10,9 +10,7 @@ aliases:
 
 {{< include "dev-envs-changing.md" >}}
 
-{{% experimental title="Beta" %}}
-The Dev Environments feature is currently in [Beta](/manuals/release-lifecycle.md#beta). 
-{{% /experimental %}}
+{{< summary-bar feature_name="Dev Environments" >}}
 
 Dev Environments let you create a configurable developer environment with all the code and tools you need to quickly get up and running. 
 

@@ -14,7 +14,7 @@ params:
       text: New
 ---
 
-{{< introduced desktop 4.35.0 "../../desktop/release-notes.md#4350" >}}
+{{< summary-bar feature_name="USB/IP support" >}}
 
 > [!NOTE]
 >

@@ -13,13 +13,15 @@ aliases:
 - /desktop/vmm/
 ---
 
+{{< summary-bar feature_name="VMM" >}}
+
 The Virtual Machine Manager (VMM) in Docker Desktop for Mac is responsible for creating and managing the virtual machine used to run containers. Depending on your system architecture and performance needs, you can choose from multiple VMM options in Docker Desktop's [settings](/manuals/desktop/settings-and-maintenance/settings.md#general). This page provides an overview of the available options.
 
-## Docker VMM (Beta)
+## Docker VMM
 
-Docker VMM is a new, container-optimized hypervisor introduced in Docker Desktop 4.35 and available on Apple Silicon Macs only. Its enhanced speed and resource efficiency makes it an ideal choice for optimizing your workflow. 
+Docker VMM is a new, container-optimized hypervisor introduced in Docker Desktop 4.35 and available on Apple Silicon Macs only. Its enhanced speed and resource efficiency makes it an ideal choice for optimizing your workflow.
 
-Docker VMM brings exciting advancements specifically tailored for Apple Silicon machines. By optimizing both the Linux kernel and hypervisor layers, Docker VMM delivers significant performance enhancements across common developer tasks. 
+Docker VMM brings exciting advancements specifically tailored for Apple Silicon machines. By optimizing both the Linux kernel and hypervisor layers, Docker VMM delivers significant performance enhancements across common developer tasks.
 
 Some key performance enhancements provided by Docker VMM include:
  - Faster I/O operations: With a cold cache, iterating over a large shared filesystem with `find` is 2x faster than when the Apple Virtualization Framework is used.
@@ -31,9 +33,7 @@ These improvements directly impact developers who rely on frequent file access a
 >
 > Docker VMM requires a minimum of 4GB of memory to be allocated to the Docker Linux VM. The memory needs to be increased before Docker VMM is enabled, and this can be done from the **Resources** tab in **Settings**.
 
-Docker VMM is based on [libkrun](https://github.com/containers/libkrun).
-
-### Known issues 
+### Known issues
 
 As Docker VMM is still in Beta, there are a few known limitations:
 

@@ -8,11 +8,7 @@ aliases:
 - /desktop/wasm/
 ---
 
-{{% experimental title="Beta" %}}
-The Wasm feature is currently in [Beta](/manuals/release-lifecycle.md#beta).
-We recommend that you do not use this feature in production environments as
-this feature may change or be removed from future releases.
-{{% /experimental %}}
+{{< summary-bar feature_name="Wasm workloads" >}}
 
 Wasm (short for WebAssembly) is a fast, light alternative to the Linux and
 Windows containers you’re using in Docker today (with

@@ -9,6 +9,8 @@ aliases:
  - /desktop/allow-list/
 ---
 
+{{< summary-bar feature_name="Allow list" >}}
+
 This page contains the domain URLs that you need to add to a firewall allowlist to ensure Docker Desktop works properly within your organization.
 
 ## Domain URLs to allow

@@ -11,9 +11,7 @@ params:
       text: EA
 ---
 
-{{% restricted title="Early Access" %}}
-The PKG installer is currently an [Early Access](/manuals/release-lifecycle.md) feature and is available to all company and organization owners with a Business subscription and Docker Desktop version 4.36 and later.
-{{% /restricted %}}
+{{< summary-bar feature_name="PKG installer" >}}
 
 The PKG package supports various MDM (Mobile Device Management) solutions, making it ideal for bulk installations and eliminating the need for manual setups by individual users. With this package, IT administrators can ensure standardized, policy-driven installations of Docker Desktop, enhancing efficiency and software management across their organizations.
 

@@ -9,6 +9,8 @@ aliases:
 - /desktop/setup/install/msi/use-intune/
 ---
 
+{{< summary-bar feature_name="Intune" >}}
+
 Learn how to deploy Docker Desktop for Windows and Mac using Intune, Microsoft's cloud-based device management tool. 
 
 {{< tabs >}}

@@ -19,9 +19,7 @@ aliases:
 
 This page contains information on how to install, launch and upgrade Docker Desktop on an Arch-based distribution. 
 
-> [!IMPORTANT]
->
-> This is an experimental installation package. Docker has not tested or verified the installation.
+{{< summary-bar feature_name="Docker Desktop Archlinux" >}}
 
 ## Prerequisites
 

@@ -42,9 +42,7 @@ Docker Desktop settings.
 
 ### Import builds
 
-{{% experimental title="Beta feature" %}}
-Import builds is currently in [Beta](../../release-lifecycle.md#Beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="Import builds" >}}
 
 The **Import builds** button lets you import build records for builds by other
 people, or builds in a CI environment. When you've imported a build record, it

@@ -7,10 +7,7 @@ aliases:
 - /docker-hub/builds/how-builds-work/
 ---
 
-> [!NOTE]
->
-> Automated builds require a
-> Docker Pro, Team, or Business subscription.
+{{< summary-bar feature_name="Automated builds" >}}
 
 Docker Hub can automatically build images from source code in an external
 repository and automatically push the built image to your Docker repositories.