Docker has arguably triggered innovation at an unprecedented scale for containerizing scalable applications. Red Hat's OpenShift 3.x capitalizes on this open source technology to enable a true Devops effort. Do you need OpenShift to be able to use these images? NO! The README's in the various folders can help get you going simply by using Docker.
This kiosk framework allows you to run various desktop applications in Docker containers. In the simplest case, the applications are accessed via a VNC or XRDP connection. Wouldn't it be cool if these applications could be used in a web console (a web browser)? Glyptodon's HTML5 desktop gateway, Guacamole, enables just that. They've even gone to the lengths as to Dockerize their framework. This makes it easy to string all the pieces together for a web based, Dockerized desktop kiosk.
You do not need to use Guacamole to take advantage of the barebones kiosk, but it does increase usability.
In Docker fashion, the Docker images are constructed in a layered manner.
For example, the centos/centos-vnc container simply installs the base Gnome desktop as well as a Tiger VNC server. Applications are then installed via separate Docker files using the centos-vnc image.
The CentOS images are built automatically on Docker Hub. Simply invoking a "docker pull" will allow you to obtain the desired image. Should you wish to deploy the CentOS based images to OpenShift, the images are pulled from Docker Hub. In other words, there are no build configs for these images in the yaml templates.
On the other hand, the RHEL based images will need to be constructed in your own environment. This shouldn't be a big deal; but it just takes a little more time.
If you wish to build or run a kiosk without OpenShift, I recommend you build and run the Docker containers in the following order.
1.) vnc
2.) vnc-firefox and/or vnc-eclipse
3.) xrdp
From there, I would move on to running Guacamole.
Included are a number of templates that will enable deployment.