Skip to content

fix: remove outdated screenshot #22322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 27, 2025
Merged

fix: remove outdated screenshot #22322

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e58aeed
fix: remove outdated screenshot
aevesdocker Mar 27, 2025
fe7a2e3
fix: remove outdated screenshot
aevesdocker Mar 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,6 @@ Enforced settings appear grayed out in Docker Desktop. They can't be edited via

In addition, if Enhanced Container Isolation is enforced, developers can't use privileged containers or similar techniques to modify enforced settings within the Docker Desktop Linux VM. For example, they can't reconfigure proxy and networking, or Docker Engine.

![Proxy settings grayed out](/assets/images/grayed-setting.png)

## What's next?

- [Configure Settings Management with a `.json` file](configure-json-file.md)
Expand Down
4 changes: 1 addition & 3 deletions ...security/for-admins/hardened-desktop/settings-management/configure-json-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,4 @@ For settings to take effect:

So as not to disrupt your developers' workflow, Docker doesn't automatically mandate that developers re-launch and re-authenticate once a change has been made.

In Docker Desktop, developers see the relevant settings grayed out and the message **Locked by your administrator**.

![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png)
In Docker Desktop, developers see the relevant settings grayed out.
Binary file removed static/assets/images/grayed-setting.png
View file
Open in desktop
Binary file not shown.