Docker Hub connector
Set up the Docker Hub connector in Kaivo: authentication, configuration, the 1 BigQuery tables it syncs, and answers to common questions.
Docker Hub connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Docker Hub data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Docker Hub instead of moving it.
What is the Docker Hub connector
Section titled “What is the Docker Hub connector”Sync your Docker Hub data into BigQuery with Kaivo to track image pulls, repository activity, and adoption trends over time.
| Category | Tech |
|---|---|
| Authentication | Other |
| Setup | Self-service |
Getting started with the Docker Hub connector
Section titled “Getting started with the Docker Hub connector”- Sign up for Kaivo and create a workspace.
- Connect your Docker Hub account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Docker Hub
Section titled “Authenticating Docker Hub”Follow the steps below to connect your Docker Hub account.
Configuring the Docker Hub connector
Section titled “Configuring the Docker Hub connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Docker Username | |
| Your Docker Hub username or organization name. |
|
Tables and columns synced from Docker Hub
Section titled “Tables and columns synced from Docker Hub”Kaivo syncs 1 table from Docker Hub into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
docker_hub (20 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
user |
STRING |
The user associated with the repository. |
name |
STRING |
The name of the repository. |
namespace |
STRING |
The namespace associated with the repository. |
repository_type |
STRING |
The type of the repository. |
status |
INT64 |
The status of the repository. |
description |
STRING |
The description of the repository. |
is_private |
BOOL |
Indicates whether the repository is private. |
is_automated |
BOOL |
Indicates whether the repository is automated. |
can_edit |
BOOL |
Indicates whether the user has edit permissions for the repository. |
star_count |
INT64 |
The count of stars or likes for the repository. |
pull_count |
INT64 |
The count of pulls or downloads for the repository. |
date_registered |
STRING |
The date when the repository was registered on Docker Hub. |
status_description |
STRING |
The description of the status of the repository. |
last_updated |
STRING |
The date when the repository was last updated. |
is_migrated |
BOOL |
Indicates whether the repository has been migrated. |
collaborator_count |
INT64 |
The count of collaborators associated with the repository. |
affiliation |
STRING |
The affiliation of the user or organization that owns the repository. |
hub_user |
STRING |
The user associated with the repository on Docker Hub. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: docker_hub__content_types
Section titled “Subtable: docker_hub__content_types”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: docker_hub__media_types
Section titled “Subtable: docker_hub__media_types”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Docker Hub sync works
Section titled “How the Docker Hub sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Docker Hub supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Docker Hub?
Section titled “How long does the initial sync take for Docker Hub?”It depends on how much history is in your Docker Hub account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Docker Hub’s schema changes?
Section titled “What happens when Docker Hub’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Docker Hub, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Docker Hub instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Docker Hub connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Docker Hub data
Section titled “Common use cases for Docker Hub data”Pull tracking
Section titled “Pull tracking”Use docker_hub data to monitor image pulls and repository usage over time.
Repository view
Section titled “Repository view”Report on your Docker Hub repositories alongside your other data.
Adoption trends
Section titled “Adoption trends”Track how usage of your published images changes over time.
Use Docker Hub data in your AI and BI tools
Section titled “Use Docker Hub data in your AI and BI tools”Once Docker Hub data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Docker Hub data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Docker Hub connector pricing and plan details.