From a789764281cb809c7c21a342f8fcfb34ab594fa8 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Thu, 15 Jan 2026 11:32:19 +0100 Subject: [PATCH] Document how to use extension private marketplace with settings managed via admin console Signed-off-by: Guillaume Tardif --- content/manuals/extensions/private-marketplace.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/content/manuals/extensions/private-marketplace.md b/content/manuals/extensions/private-marketplace.md index a828d160dd58..3ba7edb66cc5 100644 --- a/content/manuals/extensions/private-marketplace.md +++ b/content/manuals/extensions/private-marketplace.md @@ -61,10 +61,18 @@ This creates 2 files: - `admin-settings.json`, which activates the private marketplace feature once it’s applied to Docker Desktop on your developers’ machines. - `extensions.txt`, which determines which extensions to list in your private marketplace. +> [!IMPORTANT] +> +> If your org is using [settings management](/manuals/enterprise/security/hardened-desktop/settings-management/_index.md) via [Admin console](manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console/_index.md), you will not need the admins-settings.json file. Just delete the generated file and keep only `extensions.txt` at this stage. + ## Step two: Set the behaviour The generated `admin-settings.json` file includes various settings you can modify. +> [!IMPORTANT] +> +> If your org is managing settings via [Admin console](manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console/_index.md), you will define the same settings in the admin console instead of admins-settings.json. + Each setting has a `value` that you can set, including a `locked` field that lets you lock the setting and make it unchangeable by your developers. - `extensionsEnabled` enables Docker Extensions. @@ -174,6 +182,10 @@ It's recommended that you try the private marketplace on your Docker Desktop ins 2. Quit and re-open Docker Desktop. 3. Sign in with a Docker account. +> [!IMPORTANT] +> +> > If your org is managing settings via [Admin console](manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console/_index.md), with Docker Desktop version lower than 4.59 you will need to manually delete `admin-settings.json` that has been created in the target folder by the `apply` command before step 2. + When you select the **Extensions** tab, you should see the private marketplace listing only the extensions you have allowed in `extensions.txt`. ![Extensions Private Marketplace](/assets/images/extensions-private-marketplace.webp) @@ -183,7 +195,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: -* `admin-settings.json` +* `admin-settings.json` (except if your org is managing settings via [Admin console](manuals/enterprise/security/hardened-desktop/settings-management/configure-admin-console/_index.md)) * the entire `extension-marketplace` folder and its subfolders These files must be placed on developer's machines. Depending on your operating system, the target location is (as mentioned above):