Docker Hub Image Search Scraper is a BrowserAct Bot template for collecting structured container image records from public Docker Hub search results. Configure a keyword and result count, then run the Bot to return ranked image metadata for DevOps research, dependency discovery, container catalog monitoring, competitive analysis, or automation workflows.
What Does BrowserAct Docker Hub Image Search Scraper Do?
This template opens Docker Hub search for your keyword, extracts public image result cards, follows pagination when needed, and returns one structured record per container image.
Key Features
- Extract public Docker Hub search results without requiring a login.
- Capture rank, image name, image URL, publisher, description, pull count, star count, official image status, verified publisher status, update time, and keyword.
- Configure base URL, keyword, and count.
- Continue through Docker Hub result pages until the requested count is reached.
- Keep image metadata ready for DevOps dashboards, security review, catalog analysis, and agent workflows.
What Data Can I Extract from Docker Hub?
| Field | Description |
|---|---|
rank |
Search result position. |
image_name |
Container image or repository name. |
image_url |
Public Docker Hub image URL. |
publisher |
Publisher, namespace, official image label, or organization shown on the card. |
description |
Image description when visible. |
pull_count |
Pull count shown on the result card. |
star_count |
Star count when visible. |
official_image |
Whether the result is marked as a Docker Official Image. |
verified_publisher |
Whether the result is marked as a verified publisher. |
last_updated |
Last updated time shown by Docker Hub. |
search_keyword |
Keyword used for the run. |
How to Use Docker Hub Image Search Scraper
- Click Run task.
- Enter the Docker Hub base URL.
- Enter an image name, technology, vendor, or use-case keyword.
- Set how many image records to collect.
- Run the Bot and review the structured container image results.
- Reuse the Bot with another keyword or connect the output to your workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://hub.docker.com |
Docker Hub base URL without a trailing slash. |
keyword |
Yes | nginx |
Search keyword sent as the q query parameter. |
count |
Yes | 20 |
Maximum number of image records to return. |
Example Output
{
"results": [
{
"rank": 1,
"image_name": "Nginx",
"image_url": "https://hub.docker.com/hardened-images/catalog/dhi/nginx",
"publisher": "Docker Hardened Image",
"description": "nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server.",
"pull_count": "1M+",
"star_count": "",
"official_image": false,
"verified_publisher": false,
"last_updated": "about 9 hours ago",
"search_keyword": "nginx"
}
]
}
How Does it Work?
BrowserAct constructs a public Docker Hub search URL from base_url and keyword, opens the search results page, and reads each visible image result card. The Bot maps each card into a ranked record with image name, URL, publisher, description, pull count, star count, official image flag, verified publisher flag, last updated time, and keyword.
When count is higher than the first result page, BrowserAct follows Docker Hub pagination using the public page parameter. Docker Hub may cap the number of public search pages for broad keywords, so the Bot stops when it reaches the requested count or when no more public results are available.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the Data You Need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.
Step 2: Let BrowserAct Build and Test the Bot
BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.
Step 3: Run the Bot and Review the Result
When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.
Why Scrape Docker Hub Image Search Results?
Docker Hub search data helps teams discover container images, compare publishers, review official and verified status, monitor pull counts, map container ecosystems, and route image metadata into DevOps reports, catalogs, dashboards, or agents.
Who Can Use This Template?
- DevOps teams researching container images and alternatives.
- Platform teams building internal image catalogs.
- Security teams reviewing publisher and official image status.
- Developer relations teams monitoring container ecosystem visibility.
- Automation builders routing image metadata into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of Docker Hub image records returned. Docker Hub typically shows 30 results per page, and broad searches may have a public page cap.
Automation and Export
BrowserAct returns structured Docker Hub image records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
