Ververica Platform Docker Images

For convenience, Ververica hosts a public Docker registry that contains images of all Ververica Platform components. You can either use this registry directly or host the images yourself in a private registry. Please find more details for both options below.

For information how use custom images with Ververica Platform please see Custom Images.

Ververica Platform Public Registry

The registry is hosted at registry.platform.data-artisans.net, and the images of a particular Ververica Platform version are published under the specific version prefix.

For Ververica Platform 2.0 the following images are available.

Repository Tag Additional Tags
v2.0/vvp-appmanager 2.0.1  
v2.0/vvp-artifact-fetcher 2.0.1  
v2.0/vvp-gateway 2.0.1  
v2.0/vvp-ui 2.0.1  
v2.0/flink 1.8.2-stream1-scala_2.11 1.8, 1.8.2, 1.8.2-stream1
v2.0/flink 1.8.2-stream1-scala_2.12  
v2.0/flink 1.9.0-stream1-scala_2.11  
v2.0/flink 1.9.0-stream1-scala_2.12 1.9.0, 1.9.0-stream1
v2.0/flink 1.9.1-stream1-scala_2.11  
v2.0/flink 1.9.1-stream1-scala_2.12 1.9, 1.9.1, 1.9.1-stream1

Attention

The registry hosted by Ververica is provided without SLA. If you require availability guarantees, you should import the Ververica Platform images into your own registry.

Private Registry

If you wish to host the Ververica Platform images yourself, you will have to pull, re-tag, and push the images accordingly. Below is a snippet showing one approach to make this easier, updating REGISTRY and IMAGE respectively to suit your case.

$ REGISTRY=registry.acme.inc; \
   IMAGE=v2.0/vvp-appmanager:2.0.1; \
   docker pull registry.platform.data-artisans.net/${IMAGE} && \
   docker tag registry.platform.data-artisans.net/${IMAGE} ${REGISTRY}/${IMAGE} && \
   docker push ${REGISTRY}/${IMAGE}

Note

These snippets are provided as examples, and may need to be adapted for your particular operating system/environment.

Private Offline Registry

If you’re using a private registry that has restricted network access, you may need to be able to fetch the images, move them, and then load them into the target registry. Below is a simple recipe which builds on the one above to accomplish this.

$ REGISTRY=registry.acme.inc; \
   IMAGE=v2.0/vvp-appmanager:2.0.1; \
   ARCHIVE=$(echo ${IMAGE} | sed -e 's/.*\///g' -e 's/:/-/g').tar.gz; \
   docker pull registry.platform.data-artisans.net/${IMAGE} && \
   docker tag registry.platform.data-artisans.net/${IMAGE} ${REGISTRY}/${IMAGE} && \
   docker save ${REGISTRY}/${IMAGE} | gzip > ${ARCHIVE}

$ REGISTRY=registry.acme.inc; \
   IMAGE=v2.0/vvp-appmanager:2.0.1; \
   ARCHIVE=$(echo ${IMAGE} | sed -e 's/.*\///g' -e 's/:/-/g').tar.gz; \
   gunzip -c ${ARCHIVE} | docker load && \
   docker push ${REGISTRY}/${IMAGE}

Note

These snippets are provided as examples, and may need to be adapted for your particular operating system/environment.