ENGDOCS-2181c #21419
Open
ENGDOCS-2181c #21419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
github-actions
bot
added
area/desktop
| Settings Management in the Docker Admin Console is an [early access](/release-lifecycle#early-access-ea) feature and is available to Docker Business customers only. | ||
| {{% /restricted %}} | ||
|
|
||
| This page contains information for administrators on how to configure Settings Management with the Docker Admin Console to specify and lock configuration parameters to create a standardized Docker Desktop environment across your Docker company or organization. |
There was a problem hiding this comment.
Suggested change
| This page contains information for administrators on how to configure Settings Management with the Docker Admin Console to specify and lock configuration parameters to create a standardized Docker Desktop environment across your Docker company or organization. | |
| This page contains information for administrators on how to configure Settings Management with the Docker Admin Console. You can specify and lock configuration parameters to create a standardized Docker Desktop environment across your company or organization. |
There was a problem hiding this comment.
just a suggestion for readability
| ## Prerequisites | ||
|
|
||
| - [Download and install Docker Desktop 4.36.0 or later](/manuals/desktop/release-notes.md). | ||
| - Make sure you have [verified your domain](/manuals/security/for-admins/single-sign-on/configure.md#step-one-add-and-verify-your-domain) |
There was a problem hiding this comment.
Suggested change
| - Make sure you have [verified your domain](/manuals/security/for-admins/single-sign-on/configure.md#step-one-add-and-verify-your-domain) | |
| - [Verify your domain](/manuals/security/for-admins/single-sign-on/configure.md#step-one-add-and-verify-your-domain). |
There was a problem hiding this comment.
just a suggestion for simplicity
Comment on lines
+24
to
+27
| - [Enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md). This is | ||
| because the Settings Management feature requires a Docker Business | ||
| subscription and therefore your Docker Desktop users must authenticate to your | ||
| organization for configurations to take effect. |
There was a problem hiding this comment.
Suggested change
| - [Enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md). This is | |
| because the Settings Management feature requires a Docker Business | |
| subscription and therefore your Docker Desktop users must authenticate to your | |
| organization for configurations to take effect. | |
| - [Enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md). The Settings Management feature requires a Docker Business subscription, therefore your Docker Desktop users must authenticate to your | |
| organization for configurations to take effect. |
| > | ||
| > Before setting a global settings policy, it is recommended that you first test it as a user-specific policy to make sure you're happy with the changes before proceeding. | ||
|
|
||
| 6. Configure the settings for the policy. Go through each setting and select your chosen setting state. You can choose |
There was a problem hiding this comment.
Suggested change
| 6. Configure the settings for the policy. Go through each setting and select your chosen setting state. You can choose | |
| 6. Configure the settings for the policy. Go through each setting and select your chosen setting state. You can choose: |
| > [!NOTE] | ||
| > | ||
| > Settings are synced to Docker Desktop and the CLI when a user is signed in and starts Docker Desktop, and then every 60 minutes. | ||
| If your settings policy needs to be rolled back, either delete the policy or edit the policy to set individual settings to **User-defined**. |
There was a problem hiding this comment.
Suggested change
| If your settings policy needs to be rolled back, either delete the policy or edit the policy to set individual settings to **User-defined**. | |
| If your settings policy needs to be rolled back, either delete the policy or edit the policy to set individual settings to **User-defined**. |
There was a problem hiding this comment.
whitespace nit
| --- | ||
|
|
||
| > [!NOTE] | ||
| > | ||
| > Settings Management is available to Docker Business customers only. | ||
|
|
||
| This page contains information on how to configure Settings Management to specify and lock configuration parameters to create a standardized Docker Desktop environment across the organization. | ||
| This page contains information on how to configure Settings Management with an `admin-settings.json` file to specify and lock configuration parameters to create a standardized Docker Desktop environment across the organization. |
There was a problem hiding this comment.
Suggested change
| This page contains information on how to configure Settings Management with an `admin-settings.json` file to specify and lock configuration parameters to create a standardized Docker Desktop environment across the organization. | |
| This page contains information on how to configure Settings Management with an `admin-settings.json` file. You can specify and lock configuration parameters to create a standardized Docker Desktop environment across your company or organization. |
sarahsanders-docker
requested changes
Nov 13, 2024
dvdksn
reviewed
Nov 13, 2024
| @@ -24,6 +24,7 @@ Ddosify | |||
| Debootstrap | |||
| Dev Environments? | |||
| Django | |||
| Docker Admin Console | |||
There was a problem hiding this comment.
Not needed; fixed in #21422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Replaces #20646 that was so old it was still using the
toc.yamlfile.SME reviews complete. Just need editorial
Related issues or tickets
Reviews