Cory Snider 3991faf464 Move filtered registry search out of image service ... SearchRegistryForImages does not make sense as part of the image service interface. The implementation just wraps the search API of the registry service to filter the results client-side. It has nothing to do with local image storage, and the implementation of search does not need to change when changing which backend (graph driver vs. containerd snapshotter) is used for local image storage. Filtering of the search results is an implementation detail: the consumer of the results does not care which actor does the filtering so long as the results are filtered as requested. Move filtering into the exported API of the registry service to hide the implementation details. Only one thing---the registry service implementation---would need to change in order to support server-side filtering of search results if Docker Hub or other registry servers were to add support for it to their APIs. Use a fake registry server in the search unit tests to avoid having to mock out the registry API client. Signed-off-by: Cory Snider <csnider@mirantis.com>		2023-03-10 18:36:33 -05:00
..
docker-proxy	cmd/docker-proxy: add "-v / --version" flag	2022-12-27 22:26:57 +01:00
dockerd	Move filtered registry search out of image service	2023-03-10 18:36:33 -05:00