From 3cf9e5ba1dd8a6f7204f7e071c19e62d3235932b Mon Sep 17 00:00:00 2001 From: Jerae Duffin Date: Tue, 24 May 2022 10:03:22 -0500 Subject: [PATCH] updated link --- docker-hub/registry-access-management.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docker-hub/registry-access-management.md b/docker-hub/registry-access-management.md index 2063b03cf6..2b4e74c9d6 100644 --- a/docker-hub/registry-access-management.md +++ b/docker-hub/registry-access-management.md @@ -42,9 +42,10 @@ Download Docker Desktop 4.8 or a later release. ## Creating a registry.json file -When creating a registry.json file, ensure that the developer is a member of at least one organization in Docker Hub. If the registry.json file matches at least one organization the developer is a member of, they can sign in to Docker Desktop and access all their organizations. Learn more on how to create a registry.json file on [Windows](/docker-hub/configure-sign-in/#windows) or [Mac](docker-hub/configure-sign-in/#mac). +When creating a `registry.json` file, ensure that the developer is a member of at least one organization in Docker Hub. If the `registry.json` file matches at least one organization the developer is a member of, they can sign in to Docker Desktop and access all their organizations. Learn more on how to create a registry.json file on [Windows](/configure-sign-in/#windows) or [Mac] +(/configure-sign-in/#mac). -{## Verify the restrictions +## Verify the restrictions The new Registry Access Management policy should be in place after the developer successfully authenticates to Docker Desktop using their organization credentials. The developer can attempt to pull an image from a disallowed registry via the Docker CLI. They will then receive an error message that your organization disallows this container registry.