Denodo on Docker FAQ
The prerequisites are driven by the Docker version support for each given OS platform. One can use either the CE (community edition) or the EE (Enterprise edition). Kindly check Docker’s support policy for each of the above. In order for Denodo to work correctly, you should also meet the minimum requirements for the Denodo Platform, found in the documentation.
You can also find more details about the prerequisites on how to run the Denodo Platform Container in the quick startup guide, provided by Denodo.
The Docker container image is available through the Denodo Support site. Look for the image with the name “denodo-container-8.0”.
Once downloaded, follow the basic instructions of the quick start guide. Currently, the Docker container is not available on the Docker Store, but we are actively looking into it.
The Denodo Platform Container image can be used either with standalone Denodo Licenses (like the Denodo Express License or an Evaluation License) or with licenses managed by a Denodo Solution Manager. There is no separate license for the container version. If you are running multiple Docker images on the same host, they are counted as different licenses for the Denodo Platform server.
Yes, one can certainly run the Denodo Platform Docker Container on the AWS Container service (EKS). There are no additional steps from Denodo’s perspective.
It is quick and easy, but hit helps to have a basic understanding and knowledge of containers and operating systems. The steps are outlined in the quick start guide.
Denodo supports the Denodo Platform software running in the container. The support team will help troubleshoot any issue with the Denodo Platform running in the container, but if the issue is specific to the Docker container engine, the user would need to follow up with Docker. It is possible to get the Docker engine as part of an OS distribution (such as RedHat or Suse Linux) or directly from Docker. You would need to engage the appropriate vendor for troubleshooting and support.
Depending on your Docker installation, you may need root privileges to load the Denodo Platform Container image on Docker.
Docker provides a simplified way of packaging applications in a single container for distribution. One can run multiple containers per host but one still needs to take into account the available resources. You could run multiple Denodo VDP servers in a container format on a single host. Or you could create and run a separate container for the Denodo Scheduler and the VDP server, but there is a tradeoff in terms of managing multiple containers.
We recommend that if you are running a single instance of the Denodo Platform, keep all the Denodo processes, such as VDP server or Denodo Scheduler, in a single container, and keep the VDP admin tool outside of the container. If you run multiple copies of the Denodo Platform, it is better to maintain a single container for the scheduler, connecting to multiple containers that each run an instance of the Denodo Platform.