From af9122da4eface0b58b2ee127bb5111c8c27a820 Mon Sep 17 00:00:00 2001 From: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com> Date: Fri, 12 May 2023 08:44:03 -0700 Subject: [PATCH] Add multiple device deployment to registry.json (#17302) Signed-off-by: Craig Osterhout --- docker-hub/configure-sign-in.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docker-hub/configure-sign-in.md b/docker-hub/configure-sign-in.md index 354534467b..6f088fa694 100644 --- a/docker-hub/configure-sign-in.md +++ b/docker-hub/configure-sign-in.md @@ -1,5 +1,6 @@ --- description: Configure registry.json to enforce users to sign into Docker Desktop +toc_max: 2 keywords: authentication, registry.json, configure, title: Configure registry.json to enforce sign-in --- @@ -21,6 +22,10 @@ Deploying a `registry.json` file and forcing users to authenticate is not requir {% include configure-registry-json.md %} +## Deploy registry.json to multiple devices + +The previous instructions explain how to create and deploy a registry.json file to a single device. To automatically deploy the registry.json to multiple devices, you must use a third-party solution, such as a mobile device management solution. You can use the previous instructions along with your third-party solution to remotely deploy the registry.json file, or remotely install Docker Desktop with the registry.json file. For more details, see the documentation of your third-party solution. + ## Verify the changes After you’ve created the `registry.json` file and deployed it onto the users’ machines, you can verify whether the changes have taken effect by asking users to start Docker Desktop.