Vertica docker deployment (single container version).
In the beginning it was inspired by jbfavre docker-vertica repo.
It provides:
- Dockerfiles per OS family
- Entrypoint script running under database OS user (default dbadmin)
- Environment setting scripts
- Scripts for loading of VMART schema.
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.
Vertica™, the Vertica Analytics Platform™, and FlexStore™ are trademarks of Micro Focus International plc.
Vertica:
- 9.x
- 10.x
CentOS
- 7.9
- 8.3
Ubuntu
- 16.04
- 18.04
Debian
- Jessie
- Stretch
Most likely the deployment will work for future versions of Vertica and CentOS / Debian.
It is necessary to prepare separate Dockerfile for other OS families.
First you have to download Vertica RPM/DEB package, either Community Edition(registration required) or you can download Enterprise edition, if you are Vertica customer.
Store RPM/DEB into packages folder.
Easiest way to build images is to use build.sh script:
Usage: ./build.sh -v <vertica version> -f <OS family> -o <OS version> [-r <image name prefix>] [-p]
Options are:
-v - Vertica version, e.g. 10.0.1-5
-f - OS family, e.g. CentOS
-o - OS version of base image, e.g. 7.9.2009, 8.3.2011, ubuntu:18.04
-r - Image name prefix, a path to repository, e.g. 123456789012.dkr.ecr.eu-central-1.amazonaws.com/databases
-p - Push built image into repository defined by the image name prefix (-r)
-h - show help
Example:
# Build Vertica 10.0.1-5 with CentOS 7.9 and push the image into an AWS repository
./build.sh -v 10.0.1-5 -f CentOS -o 8.3.2011 -r 123456789012.dkr.ecr.eu-central-1.amazonaws.com -p
# Full image path will be:
# 123456789012.dkr.ecr.eu-central-1.amazonaws.com/vertica:10.0.1-5.CentOS_8.3.2011
You may need to customize other parameters, here is the full list:
docker build -f Dockerfile_CentOS \
--build-arg vertica_version=10.0.1-5 \
--build-arg os_version=8.3.2011 \
# Both Vertica OS user and implicit superadmin DB user
--build-arg vertica_db_user=mycustomuser \
--build-arg vertica_db_group=mycustomgroup \
# Database name
--build-arg vertica_db_name=mycustomname \
# Start and end years populated into VMART date_dimension table
--build-arg vmart_start_year=2000 \
--build-arg vmart_end_year=2100 \
# Remove packages, which you do not need, to significantly reduce size of the image (separated by space)
--build-arg remove_packages='voltagesecure MachineLearning' \
-t 123456789012.dkr.ecr.eu-central-1.amazonaws.com/vertica:10.0.1-5.CentOS_8.3.2011 .
We recommend to run containers with persisted volumes.
docker run -p 5433:5433 \
-v /path/to/vertica_data:/data \
--name vertica \
123456789012.dkr.ecr.eu-central-1.amazonaws.com/vertica:10.0.1-5.CentOS_8.3.2011
After you store it into docker-compose.yaml file, you can simply run:
docker-compose up -d vertica
There is a naive skeleton of integration tests for validation of the current state and for inspiration. It can be configured in tests/config.yaml. Path to a test config file can be redefined by environment variable VERTICA_IMAGE_TEST_CONFIG. For each required combination of OS / Vertica version the corresponding image is build, the container is started and tests are executed. All available customizations of build / run are applied and tested.
Run tests:
pip3 install requirements_tests.txt
pytest -vv tests
# Optionally it is possible to test loading of VMART schema:
pytest -vv tests --test-vmart
# Use different config file
VERTICA_IMAGE_TEST_CONFIG=tests/config_full.yaml pytest -vv tests
There is and option to define several pytest.ini files with different configurations and pass them to pytest:
pytest -c pytest_custom.ini -vv tests
It is possible to configure various aspects of Vertica in container runtime by injecting corresponding environment variables.
- Docker run
docker run -p 5433:5433 -d \ -e TZ='Europe/Prague' \ 123456789012.dkr.ecr.eu-central-1.amazonaws.com/vertica:10.0.1-5.CentOS_8.3.2011 - Docker-compose
- docker-compose.yaml example
- Run example with inline variable setting
docker-compose up -d -e VMART_LOAD_DATA=y vertica
List of available configuration parameters:
- VMART_LOAD_DATA
- Set value to "y" to enable generating data and loading them into VMART schema
- More info about the schema can be found on official web site
- APP_DB_USER
- Name of additional database user, who should be created
- This user is created only if this variable is set
- Pseudosuperuser role is granted and enabled to the user
- APP_DB_PASSWORD
- Password of APP_DB_USER
- If it is not set, password is empty
- TZ: "${VERTICA_CUSTOM_TZ:-Europe/Prague}"
- Customize timezone of database
- Vertica does not contain all time zones - uncomment a workaround solution in Dockerfiles (linking system time zones), if you want to set such a time zone
- Setting it like this allows you to override it from your environment by setting VERTICA_CUSTOM_TZ variable
- DEBUG_FAILING_STARTUP
- For development purposes. When you set the value to "y", entrypoint script does not end in case of failure, so you can investigate those failures
Default entry point is localhost:5433, but it is possible to configure custom port during container startup as described in previous chapters.
It is possible to connect to dbadmin user with empty password or to connect to APP_DB_USER using APP_DB_PASSWORD.
# Pure docker (we named the container in docker run statement above)
docker exec -it vertica bash -l
# docker compose
docker-compose exec vertica bash -l
Environment of dbadmin user is extended to be user-friendly, check vertica_env.sh and .vsqlrc scripts for more details.
Place custom scripts into folder ".docker-entrypoint-initdb.d", the entry point script executes them during startup of container.
Scripts are executed in lexicographical order.
Supported extensions are:
- sql - SQL commands executed through vsql
- sh - shell scripts
You have to mount .docker-entrypoint-initdb.d local folder into docker container /docker-entrypoint-initdb.d/ folder. Check examples in docker-compose sections here.