docker · sarahsanders-docker · Dec 18, 2024 · Dec 18, 2024 · Dec 18, 2024 · Dec 18, 2024
@@ -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 >}}

@@ -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,11 @@ 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" >}}

@@ -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

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 >}}

@@ -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

@@ -5,18 +5,14 @@ title: Configure a private marketplace for extensions
 tags: [admin]
 linkTitle: Configure a private marketplace
 weight: 30
-aliases: 
+aliases:
  - /desktop/extensions/private-marketplace/
 ---
 
-{{% experimental title="Beta" %}}
-This feature is currently in [Beta](/manuals/release-lifecycle.md#beta). It is available to Docker Business customers only.
-{{% /experimental %}}
+{{< summary-bar feature_name="Private marketplace" >}}
 
 Learn how to configure and set up a private marketplace with a curated list of extensions for your Docker Desktop users.
 
-It is designed specifically 
-
 Docker Extensions' private marketplace is designed specifically for organizations who don’t give developers root access to their machines. It makes use of [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) so administrators have complete control over the private marketplace.
 
 ## Prerequisites
@@ -85,7 +81,7 @@ Each setting has a `value` that you can set, including a `locked` field that let
 
 To find out more information about the `admin-settings.json` file, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md).
 
-## Step three: List allowed extensions 
+## Step three: List allowed extensions
 
 The generated `extensions.txt` file defines the list of extensions that are available in your private marketplace.
 
@@ -99,14 +95,14 @@ docker/disk-usage-extension:0.2.8
 
 If no tag is provided, the latest tag available for the image is used. You can also comment out lines with `#` so the extension is ignored.
 
-This list can include different types of extension images: 
- 
+This list can include different types of extension images:
+
 - Extensions from the public marketplace or any public image stored in Docker Hub.
 - Extension images stored in Docker Hub as private images. Developers need to be signed in and have pull access to these images.
 - Extension images stored in a private registry. Developers need to be signed in and have pull access to these images.
- 
+
 > [!IMPORTANT]
-> 
+>
 > Your developers can only install the version of the extension that you’ve listed.
 
 ## Step four: Generate the private marketplace
@@ -139,7 +135,7 @@ $ /opt/docker-desktop/extension-admin generate
 
 This creates an `extension-marketplace` directory and downloads the marketplace metadata for all the allowed extensions.
 
-The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc. 
+The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc.
 
 ## Step five: Test the private marketplace setup
 
@@ -186,7 +182,7 @@ When you select the **Extensions** tab, you should see the private marketplace l
 
 Once you’ve confirmed that the private marketplace configuration works, the final step is to distribute the files to the developers’ machines with the MDM software your organization uses. For example, [Jamf](https://www.jamf.com/).
 
-The files to distribute are: 
+The files to distribute are:
 * `admin-settings.json`
 * the entire `extension-marketplace` folder and its subfolders
 

@@ -5,9 +5,7 @@ description: Integrate Docker Scout using the GitHub app to get remediation advi
 keywords: scout, github, integration, image analysis, supply chain, remediation, source code
 ---
 
-{{% experimental title="Beta feature" %}}
-The GitHub integration is currently in [Beta](../../../release-lifecycle.md#Beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="Docker Scout GitHub" >}}
 
 The GitHub app integration for Docker Scout grants Docker Scout access to your
 source code repository on GitHub. This improved visibility into how your image

@@ -4,9 +4,7 @@ description: Learn how Docker Scout can help you improve your software quality a
 keywords: scout, supply chain, security, remediation, automation
 ---
 
-{{% experimental title="Beta feature" %}}
-Remediation with Docker Scout is currently in [Beta](../../release-lifecycle.md#Beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="Remediation with Docker Scout" >}}
 
 Docker Scout helps you remediate supply chain or security issues by providing
 recommendations based on policy evaluation results. Recommendations are

@@ -6,11 +6,7 @@ description: |
 keywords: scout, health scores, evaluation, checks, grades, docker hub
 ---
 
-{{% restricted title="Beta" %}}
-Health scores is a [Beta](/release-lifecycle/#beta) feature of Docker Scout.
-The feature is only available to organizations selected to participate in the
-early access program.
-{{% /restricted %}}
+{{< summary-bar feature_name="Docker Scout health scores" >}}
 
 Docker Scout health scores provide a security assessment, and overall supply
 chain health, of images on Docker Hub, helping you determine whether an image

@@ -6,9 +6,7 @@ keywords: docker hub, security, OAT, organization access token
 linkTitle: Organization access tokens (Beta)
 ---
 
-{{% experimental title="Beta" %}}
-The organization access tokens feature is currently in [Beta](../../release-lifecycle.md#beta).
-{{% /experimental %}}
+{{< summary-bar feature_name="OATs" >}}
 
 > [!WARNING]
 >

@@ -11,9 +11,7 @@ aliases:
 weight: 30
 ---
 
-> [!NOTE]
->
-> Registry Access Management is available to [Docker Business](/manuals/subscription/details.md) customers only.
+{{< summary-bar feature_name="Registry access management" >}}
 
 With Registry Access Management (RAM), administrators can ensure that their developers using Docker Desktop only access allowed registries. This is done through the Registry Access Management dashboard in Docker Hub or the Docker Admin Console.