Creating and Verifying registry.json on Mac and Linux via CLI

To use the CLI to create a `registry.json` file, run the following commands in a terminal and replace `myorg` with your organization's name. The file contents are case-sensitive and you must use lowercase letters for your organization's name. ```console $ sudo mkdir -p "/Library/Application Support/com.docker.docker" $ echo '{"allowedOrgs":["myorg"]}' | sudo tee "/Library/Application Support/com.docker.docker/registry.json" ``` This creates (or updates, if the file already exists) the `registry.json` file at `/Library/Application Support/com.docker.docker/registry.json` and includes the organization information the user belongs to. Make sure that the file has the expected content, and that the user can't edit this file, but only the administrator can. Verify that the content of the file contains the correct information: ```console $ sudo cat "/Library/Application Support/com.docker.docker/registry.json" {"allowedOrgs":["myorg"]} ``` Verify that the file has the expected permissions (`-rw-r--r--`) and ownership (`root` and `admin`): ```console $ sudo ls -l "/Library/Application Support/com.docker.docker/registry.json" -rw-r--r-- 1 root admin 26 Jul 27 22:01 /Library/Application Support/com.docker.docker/registry.json ``` > [!IMPORTANT] > > As of Docker Desktop version 4.36 and later, you can add more than one organization to a single `registry.json` file. With Docker Desktop version 4.35 and earlier, if you add more than one organization sign-in enforcement silently fails. {{< /tab >}} {{< tab name="Linux" >}} To use the CLI to create a `registry.json` file, run the following commands in a terminal and replace `myorg` with your organization's name. The file contents are case-sensitive and you must use lowercase letters for your organization's name. ```console $ sudo mkdir -p /usr/share/docker-desktop/registry $ echo '{"allowedOrgs":["myorg"]}' | sudo tee /usr/share/docker-desktop/registry/registry.json ``` This creates (or updates, if the file already exists) the `registry.json` file at `/usr/share/docker-desktop/registry/registry.json` and includes the organization information to which the user belongs. Make sure the file has the expected content and that the user can't edit this file, only the root can. Verify that the content of the file contains the correct information: ```console $ sudo cat /usr/share/docker-desktop/registry/registry.json {"allowedOrgs":["myorg"]} ``` Verify that the file has the expected permissions (`-rw-r--r--`) and ownership (`root`): ```console $ sudo ls -l /usr/share/docker-desktop/registry/registry.json -rw-r--r-- 1 root root 26 Jul 27 22:01 /usr/share/docker-desktop/registry/registry.json ``` > [!IMPORTANT] > > As of Docker Desktop version 4.36 and later, you can add more than one organization to a single `registry.json` file. With Docker Desktop version 4.35 and earlier, if you add more than one organization sign-in enforcement silently fails. {{< /tab >}} {{< /tabs >}} ## More resources - [Video: Enforce sign-in with a registry.json](https://www.youtube.com/watch?v=CIOQ6wDnJnM)

This section provides instructions for creating and verifying the `registry.json` file on both Mac and Linux systems using the command line. It includes commands for creating the directory, writing the JSON content (specifying allowed organizations in lowercase), and verifying the file content, permissions (`-rw-r--r--`), and ownership (root and admin on Mac, root on Linux). The instructions ensure that the file can only be edited by the administrator or root user. It also highlights the importance of Docker Desktop version compatibility for multi-organization sign-in enforcement and links to a relevant video resource.