dhi.io/datahub-ingestion
DataHub Ingestion
DataHub metadata ingestion CLI for emitting metadata from data sources, BI tools, and data warehouses into DataHub.
pushed 1 day ago
linux/amd64, linux/arm64
198.12 MB
for linux/amd64
353
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About DataHub Ingestion
DataHub is an open-source metadata platform for the modern data stack. The datahub CLI provided by this image extracts
metadata from data sources, BI tools, transformation tools, and data warehouses, then emits that metadata to a DataHub
backend through ingestion recipes. It is commonly run as a scheduled job (Airflow, Prefect, cron, Kubernetes CronJob) to
keep the DataHub catalog in sync with upstream systems.
This Docker Hardened DataHub Ingestion image is available in two variants matching the upstream
acryldata/datahub-ingestion layout:
- Slim variant (default): Minimal install with the most commonly used ingestion connectors (Snowflake, BigQuery, Redshift, MySQL, PostgreSQL, S3, GCS, Azure Blob Storage, ClickHouse, Glue, dbt, Looker, LookML, Tableau, Power BI, Superset, Kafka, Business Glossary). Suitable for the majority of ingestion deployments.
- Locked variant (
-locked): Hardened airgap variant. Network access to PyPI is blocked at runtime viaUV_INDEX_URLandPIP_INDEX_URLpointed at an unreachable endpoint, so the image can only run with the connectors baked in at build time. Useful for regulated environments that prohibit unaudited runtime package installation.
For more information about DataHub, visit the upstream documentation at https://docs.datahub.com/.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with zero-known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Oracle® is a registered trademark of Oracle Corporation and/or its affiliates; Oracle Instant Client is a product of Oracle Corporation. All other third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.