Skip to content

Commit e58aeed

Browse files
committed
fix: remove outdated screenshot
1 parent 402236c commit e58aeed

File tree

2 files changed

+1
-5
lines changed

2 files changed

+1
-5
lines changed

content/manuals/security/for-admins/hardened-desktop/settings-management/_index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,6 @@ Enforced settings appear grayed out in Docker Desktop. They can't be edited via
7474

7575
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.
7676

77-
![Proxy settings grayed out](/assets/images/grayed-setting.png)
78-
7977
## What's next?
8078

8179
- [Configure Settings Management with a `.json` file](configure-json-file.md)

content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -282,6 +282,4 @@ For settings to take effect:
282282
283283
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.
284284

285-
In Docker Desktop, developers see the relevant settings grayed out and the message **Locked by your administrator**.
286-
287-
![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png)
285+
In Docker Desktop, developers see the relevant settings grayed out.

0 commit comments

Comments
 (0)