Skip to content

Commit

Permalink
update ram caveat list (#18701)
Browse files Browse the repository at this point in the history
  • Loading branch information
stephaurelio authored Nov 16, 2023
1 parent 874adeb commit f4a4be6
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/security/for-admins/registry-access-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,9 +49,9 @@ The new Registry Access Management policy takes effect after the developer succe

## Caveats

There are certain limitations when using Registry Access Management; they are as follows:
There are certain limitations when using Registry Access Management:

- Windows image pulls, and image builds are not restricted
- Windows image pulls and image builds are not restricted by default. For Registry Access Management to take effect on Windows Container mode, you must allow the Windows Docker daemon to use Docker Desktop's internal proxy by selecting the [Use proxy for Windows Docker daemon](../../desktop/settings/windows.md/#proxies) setting.
- Builds such as `docker buildx` using a Kubernetes driver are not restricted
- Builds such as `docker buildx` using a custom docker-container driver are not restricted
- Blocking is DNS-based; you must use a registry's access control mechanisms to distinguish between “push” and “pull”
Expand Down

0 comments on commit f4a4be6

Please sign in to comment.