Skip to content
Docker container for Vertica Eon mode
Shell Dockerfile Makefile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Dockerfile.eondocker Improve kubernetes functionality May 11, 2019
LICENSE Initial commit Mar 21, 2018
Makefile update to new version Apr 30, 2019 Improve kubernetes functionality May 11, 2019 Improve kubernetes functionality May 11, 2019
vertica.yaml Improve kubernetes functionality May 11, 2019


Docker container for Vertica Eon mode

The goal is a Docker container for Vertica Eon mode outside AWS using S3-compatible storage such as Minio.

I've been doing most of my work using this container on Kubernetes minikube. It should be possible to stand up a single-node instance in Docker, but you'll get the best experience with minikube.

Another prerequisite: S3-compatible storage. I'm testing with the "official" Minio docker build:

As an aside, you can load data into Vertica CE/EE from Minio by setting your aws_id, aws_secret, aws_endpoint to match your Minio config.

My approach:

The Vertica CE Dockerfile and entry script were forked from

Provide a Dockerfile here to build an image with Vertica

Provide tools (scripts, etc.) to connect to the S3-compatible storage and create the Eon mode database

Provide tools to create and manage additional Vertica Eon mode nodes

TODO: finish Kubernetes orchestration. Right now, you can scale up as described below. However, I haven't quite worked out scaling down and hibernating/reviving. Feel free to submit issue reports and pull requests!

Quick start:

If you don't want to rebuild, just docker pull bryanherger/vertica_eon:latest and skip to the "Run it" step below.

You can create a single node Eon mode instance with this Dockerfile.

Download the Vertica server RPM for RHEL/CentOS from the website and place it in the packages folder.

Clone the repo and build the image with (fill in your filename in VERTICA_PACKAGE placed in packages subdirectory): docker build -f Dockerfile.eondocker --build-arg VERTICA_PACKAGE=vertica-9.2.0-6.x86_64.RHEL6.rpm -t vertica_eon .

Run it: Eon mode parameters are set with environment variables. The following options are recognized (with defaults):

  • DATABASE_NAME=eondocker
  • DATABASE_PASSWORD=[blank/no password]
  • COMMUNAL_STORAGE=s3://verticatest/db
  • AWS_REGION=us-west-1

Use the -e switch to pass variables, e.g.: sudo docker run -it -e COMMUNAL_STORAGE=s3://foo/bar -p 15433:5433 vertica_eon:latest

Note that this will expose Vertica on port 15433 rather than default. You can change -p to 5433:5433 to have Vertica on the default port. You also don't need to run interactive (-it), though it is handy for monitoring and debugging.


There's a very minimal one-node prototype definition in vertica.yaml. To try it with minikube:

Install minikube as decribed at

Start minikube: minikube start

Edit vertica.yaml and set environment variables noted above using procedure at

Create secrets (currently just ssh keys for Vertica account): sh ./

Set up the Vertica service: kubectl apply -f vertica.yaml

Get the Vertica host and port: minikube service vertica --url (sample output:

Connect to Vertica using host and port from the above output: vsql -U dbadmin -h -p 32339

Or, connect to the container and run vsql there: kubectl exec -it vertica-0 /bin/bash

If you have the hardware for it, scale up: kubectl scale --replicas=2 sts/vertica

You can’t perform that action at this time.