[Container-tools] Help needed on searching Docker images on third-party registries

Max Rydahl Andersen manderse at redhat.com
Mon Aug 24 19:05:32 UTC 2015


Yes, catalog is not usable for search.

But seems you all have same info as we found.

v1 has search, removed in v2 but eventually coming back.

sucks for users though ;/

/max

> On Mon, 2015-08-24 at 12:05 +0200, Vaclav Pavlin wrote:
>> Hi Max,
>>
>>
>> Short answer: yes, for v1 it's like:
>> http://registry.access.redhat.com/v1/search?q=*
>>
>>
>> Works also for Docker
>> Hub: https://registry.hub.docker.com/v1/search?q=fedora
>>
>>
>> I am not sure about v2 API, Pavel, do you know if there is *search* 
>> in
>> v2?
>>
>
> v2 has recently added a catalog API:
> https://github.com/docker/distribution/blob/master/docs/spec/api.md
>
> This is more like listing of everything there is in the registry 
> rather
> than search, though.
> The v2 endpoint is aimed to be very dumbed-down blob storage, so the
> facilities related to search/indexing/discovery are most likely to be
> implemented as third party services.
>
> I've already worked on scraping v2 registry data directly from file
> system:
> https://github.com/shaded-enmity/image-metadata-service/blob/master/service.py
>
> The general workflow for having *all the v2 data* on-demand is as
> follows:
>
> 1) Start listening for v2 image notifications, queue all messages
> 2) Execute file system scraper like in the link above, wait for
> completion
> 3) Process all messages from the queue and merge with the data set
> obtained from file system, rinse & repeat this step
>
> I've also created a Vagrant box for that:
>
> 1) Launches a v2 registry
> 2) Generates N-repositories with M-images each
> 3) Pushes those images/repos into the registry
> 4) Scrapes all the v2 image manifests for metadata and stores them in
> a JSON format
>
> https://github.com/shaded-enmity/ims-vagrant
>
>>
>> Vašek
>>
>>
>>
>>
>>
>> On Mon, Aug 24, 2015 at 12:01 PM, Max Rydahl Andersen
>> <manderse at redhat.com> wrote:
>>      Maybe a few missed the actual question from Xavier in his
>>      detailed email:
>>
>>              from my current understanding there does not seem to
>>              be a standard API for searching images on registries.
>>              If we want to provide support for Image Search on
>>              third party registries (I'm thinking about Red Hat
>>              registry and OpenShift v3) via plugins on top of the
>>              Docker tooling, we would need at least some endpoints
>>              to call.
>>
>>
>>              Do you have any info about that ? Is there a plan to
>>              implement a search endpoint
>>              for 
>> [docker-registry.usersys.redhat.com](http://docker-registry.usersys.redhat.com) 
>> or for other registries that customers may use to pull official 
>> Docker images ?
>>
>>      Or in short - do you guys know if there is a common docker
>>      registry search API we could target from the tooling ?
>>
>>      /max
>>      http://about.me/maxandersen
>>
>>
>>      _______________________________________________
>>      Container-tools mailing list
>>      Container-tools at redhat.com
>>      https://www.redhat.com/mailman/listinfo/container-tools
>>
>>
>>
>>
>>
>> -- 
>> Architect - Senior Software Engineer
>> Developer Experience
>> Brno, Czech Republic
>> Phone: +420 739 666 824
>>
>
>
> -- 
> Pavel Odvody <podvody at redhat.com>
> Software Engineer - EMEA ENG Developer Experience
> 5EC1 95C1 8E08 5BD9 9BBF 9241 3AFA 3A66 024F F68D
> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno


/max
http://about.me/maxandersen




More information about the Container-tools mailing list