4f221f9a12
* build(docker): refactor docker build scripts - add "build" option to docker-compose files to simplify rebuilding of images - create "start.sh" script so it's easier to override "command" in the quickstart's docker-compose file - use dockerize to wait for requisite services to start up - add a dedicated Dockerfile for kafka-setup This fixes https://github.com/linkedin/datahub/issues/1549 & https://github.com/linkedin/datahub/issues/1550
Docker Images
The easiest way to bring up and test DataHub is using DataHub Docker images which are continuously deployed to Docker Hub with every commit to repository.
- linkedin/datahub-gms
- linkedin/datahub-frontend
- linkedin/datahub-mae-consumer
- linkedin/datahub-mce-consumer
Above Docker images are created for DataHub specific use. You can check subdirectories to check how those images are generated via Dockerbuild files or how to start each container using Docker Compose. Other than these, DataHub depends on below Docker images to be able to run:
Local-built ingestion image allows you to create on an ad-hoc basis metadatachangeevent with Python script.
The pipeline depends on all the above images composing up.
Prerequisites
You need to install docker and docker-compose.
Quickstart
If you want to quickly try and evaluate DataHub by running all necessary Docker containers, you can check Quickstart Guide.