Configure allowed container registries #10371
-
Is there any allowlist configuration for registries, or a flag that would forbid access to registries not specified in I have read, and am currently using, the documentation for configuring mirrors and custom registries Let's say I want my users to be able to pull from our private registry that serves as a pull-through-cache for machine:
registries:
mirrors:
docker.io:
endpoints:
- https://myregistry.example.com/v2/docker.io
overridePath: true
skipFallback: true
config:
myregistry.example.com:
auth:
username: <user>
password: <pass> This works, but it also allows the user to pull from machine:
registries:
allowList:
- myregistry.example.com
- mcr.microsoft.com or machine:
registries:
configuredOnly: true |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Yes, there is such way (but not obvious):
Any not explicitly configured registry pull will fall to |
Beta Was this translation helpful? Give feedback.
-
Thank you the immediate response. It works great! |
Beta Was this translation helpful? Give feedback.
Yes, there is such way (but not obvious):
*
(catch-all) entry, and point it to an endpoint which doesn't work (e.g. 127.0.0.1:1), and disable fallback.Any not explicitly configured registry pull will fall to
*
, fail, will not fallback, and fail completely.