Docker Deployment
Deploying OpenMetadata in Docker is a great start! Before starting with the deployment make sure you follow all the below Prerequisites.
Prerequisites
Docker (version 20.10.0 or greater)
Docker is an open-source platform for developing, shipping, and running applications. It enables you to separate your applications from your infrastructure, so you can deliver software quickly using OS-level virtualization. It helps deliver software in packages called Containers.
To check what version of Docker you have, please use the following command.
If you need to install Docker, please visit Get Docker.
Docker Compose (version v2.2.3 or greater)
The Docker compose package enables you to define and run multi-container Docker applications. The compose command integrates compose functions into the Docker platform, making them available from the Docker command-line interface ( CLI). The Python packages you will install in the procedure below use compose to deploy OpenMetadata.
- MacOS X: Docker on MacOS X ships with compose already available in the Docker CLI.
- Linux: To install compose on Linux systems, please visit the Docker CLI command documentation and follow the instructions.
To verify that the docker compose command is installed and accessible on your system, run the following command.
Upon running this command you should see output similar to the following.
Install Docker Compose Version 2 on Linux
Follow the instructions here to install docker compose version 2
Run the following command to download the current stable release of Docker Compose
This command installs Compose V2 for the active user under $HOME directory. To install Docker Compose for all users on your system, replace
~/.docker/cli-plugins
with/usr/local/lib/docker/cli-plugins
.Apply executable permissions to the binary
Test your installation
Steps for Deploying OpenMetadata using Docker
First download the docker-compose.yml file from the release page here. The latest version is at the top of the page
- Deploying with MySQL: Download
docker-compose.yml
file from the above link. - Deploying with PostgreSQL: Download
docker-compose-postgres.yml
file from the above link.
- Deploying with MySQL: Download
Create the directory for host volumes
- Run the below command to deploy the OpenMetadata
This command will pull the docker images of Openmetadata for MySQL, OpenMetadat-Server, OpenMetadata-Ingestion and Elasticsearch.
Upon running this command you should see output similar to the following.
You can validate that all containers are up by running with command docker ps
.
In a few seconds, you should be able to access the OpenMetadata UI at http://localhost:8585
Port Mapping / Port Forwarding
For OpenMetadata-Server
We are shipping the OpenMetadata server and UI at 8585
, and the ingestion container (Airflow) at 8080
. You can change the port number's according to your requirement. As an example, You could update the ports to serve OpenMetadata Server and UI at port 80
To achieve this
- You just have to update the ports mapping of the openmetadata-server in the
docker-compose.yml
file underopenmetadata-server
docker service section.
- Once the port is updated if there are any containers running remove them first using
docker compose down
command and then recreate the containers once again by below command
For Ingestion-Server
We are shipping the OpenMetadata server and UI at 8585
, and the ingestion container (Airflow) at 8080
. You can change the port number's according to your requirement. As an example, You could update the ports to serve Ingestion Server and UI at port 80
To achieve this
- You just have to update the ports mapping of the openmetadata-server in the
docker-compose.yml
file underingestion-server
docker service section.
- Also update the Airflow environment variable in openmetadata-server section
- Once the port is updated if there are any containers running remove them first using
docker compose down
command and then recreate the containers once again by below command
PROD Deployment of OpenMetadata Using Docker
If you are planning on going to PROD, we recommend to validate below points:
- MySQL and OpenSearch (ElasticSearch) are available.
- OpenMetadata-Server require the minimum configuration of 2vCPU and 6Memory (GiB)
- OpenMetadata-Ingestion require the minimum configuration of 2vCPU and 8Memory (GiB)
- We also recommend to bind Docker Volumes for data persistence. Minimum disk space required would be 128 Gib. Learn how to do so here.
Steps for Deploying Ingestion
- Download the docker-compose.yml file from the release page here.
- Update the environment variables below for OpenMetadata-Ingestion Docker Compose backed systems to connect with Database.
Once the environment variables values with the RDS are updated then provide this environment variable file as part of docker compose command.
Steps for Deploying OpenMetadata-Server
- Download the docker-compose.yml file from the release page here.
- Update the environment variables below for OpenMetadata-Ingestion Docker Compose backed systems to connect with Database and ElasticSearch and Ingestion.
Once the environment variables values with the RDS are updated then provide this environment variable file as part of docker compose command.
Run OpenMetadata with AWS Services
If you are running OpenMetadata in AWS, it is recommended to use Amazon RDS and Amazon OpenSearch Service.
We support
- Amazon RDS (MySQL) engine version upto 8.0.29
- Amazon OpenSearch (ElasticSearch) engine version upto 7.10 or Amazon OpenSearch engine version upto 1.3
- Amazon RDS (PostgreSQL) engine version upto 14.2-R1
For Production Systems, we recommend Amazon RDS to be in Multiple Availibility Zones. For Amazon OpenSearch (or ElasticSearch) Service, we recommend Multiple Availibility Zones with minimum 3 Master Nodes.
Once you have the RDS and OpenSearch Services Setup, you can update the environment variables below for OpenMetadata Docker Compose backed systems to connect with Database and ElasticSearch.
Replace the environment variables values with the RDS and OpenSearch Service ones and then provide this environment variable file as part of docker compose command.
Troubleshooting
Java Memory Heap Issue
If your openmetadata Docker Compose logs speaks about the below issue -
This is due to the default JVM Heap Space configuration (1 GiB) being not enough for your workloads. In order to resolve this issue, head over to your custom openmetadata environment variable file and append the below environment variable
The flag Xmx
specifies the maximum memory allocation pool for a Java virtual machine (JVM), while Xms
specifies the initial memory allocation pool.
Restart the OpenMetadata Docker Compose Application using docker compose --env-file my-env-file -f docker-compose.yml up -d
which will recreate the containers with new environment variable values you have provided.
Production Deployment
If you are planning on going to PROD, we also recommend taking a look at the following other deployment strategies: