-
-
Notifications
You must be signed in to change notification settings - Fork 329
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.
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
Docker Registry >=2.8 sets catalog max entries to 1000 #306
Comments
Hi, thank you for using my project and posting issues! 🥰 Thanks for this information, I will reduce the catalog element limit in the next release and add your information about the registry configuration! |
Thank you so much for this, CATALOG_ELEMENTS_LIMIT did the trick, until this is fixed in the next release. |
Hi there ! The fix has bee published ! You can use the tag I've included some error message too for this particular use case 😉 |
For anyone using Docker Registry >=2.8: You need to either change the configuration of the Docker Registry or the UI, as the Docker Registry now defaults the maximum entries per page to 1000.
This Docker Registry configuration option does not appear to be documented in the registry repo or docs.docker.com/registry.
You will see this error from the registry:
Code:
PAGINATION_NUMBER_INVALID
Message:
invalid number of results requested
Detail:
n: 100000
Option 1: Docker Registry reconfiguration
Option 1a: YAML config
/etc/docker/registry/config.yml
reference:
https://github.com/distribution/distribution/blob/f7717b7855ca44bef5b8ccb293927a83c1d68600/configuration/configuration.go#L271
Option 1b: Environment variable
REGISTRY_CATALOG_MAXENTRIES=100000
reference:
https://docs.docker.com/registry/configuration/#override-specific-configuration-options
Option 2: UI reconfiguration
Environment variable
CATALOG_ELEMENTS_LIMIT=1000
reference:
docker-registry-ui/README.md
Line 86 in ba322e0
Change Hard-coded default
Set to
1000
:docker-registry-ui/src/components/docker-registry-ui.riot
Line 169 in ba322e0
The text was updated successfully, but these errors were encountered: