OpenShift Enterprise provided by the Container Development Environment has been upgraded to version 3.2. See the OpenShift Enterprise 3.2 Release Notes for information about new features in this version.

Red Hat Container Development Kit 2.1 offers a simple way to set up the OpenShift Enterprise Platform as a Service (PaaS), which extends the functionality of the Docker service and the Kubernetes container orchestration tool to provide a powerful and easy-to-use platform for building, deploying, and orchestrating multi-container applications and services.

A Container Development Kit Vagrant box is now available for the Hyper-V hypervisor on Microsoft Windows. Users can now set up Container Development Kit using the Hyper-V provider in Vagrant. Hyper-V is the native hypervisor in Microsoft Windows. Note that Hyper-V support is provided as Technology Preview in Red Hat Container Development Kit 2.1.

In Red Hat Container Development Kit 2.1, the size of the Vagrant Boxes has been reduced by approximately 150 MB compared to Container Development Kit 2.0.

Users can now use persistent volumes in order to preserve data between restarts of pods, OpenShift, or even the whole virtual machine that provides the Container Development Environment.

Users can now use the internal container-image registry provided by OpenShift as a stand-alone registry for docker-formatted container images on the host workstation.

Previously, the vagrant-service-manager plugin did report the status of services running within the Container Development Environment properly. With this update, a new command, status, has been added, which reports the status of required services. To use the new command, run:

$ vagrant service-manager status [service]

Substitute [service] for the service you wish to learn about: docker, kubernetes, or openshift. When used without any argument, the command lists all services and their status.

Previously, a bug in the vagrant-registration plugin prevented the automatic installation of VirtualBox Guest Additions. The bug has been fixed, and the vagrant-vbguest plugin can now be used together with the vagrant-registration plugin to install VirtualBox Guest Additions in the Container Development Kit virtual machine.

Previously, provisioning of Vagrant boxes ran only once — during the first launch of a Vagrant box using the vagrant up command after the last vagrant destroy, unless the --provision flag was used. With the latest Container Development Kit Vagrantfiles, provisioning runs with every vagrant up.

Due to a known issue that causes Red Hat JBoss Developer Studio to freeze upon start up when it attempts to launch Container Development Kit with the configuration that sets up automatic directory sharing through SSHFS, the use of the vagrant-sshfs plugin is disabled by default in Red Hat Container Development Kit 2.1.

This problem does not concern any other uses than when Container Development Kit is launched from the graphical environment of Red Hat JBoss Developer Studio.

To use SSHFS when you launch Container Development Kit from the command line, you need to use the Vagrant files that are provided in the Red Hat Container Tools ZIP in the following subdirectory: cdk/components/rhel/misc/shared_folder/.

Internal network proxies, which are used for connecting to the Internet in some networking configurations, are not supported by Container Development Kit.

DNS addressing provided by the external xip.io service is unavailable without a working Internet connection.

Using the vagrant box remove cdkv2 command fails to remove Hyper-V Vagrant boxes. To work around this issue when you wish to use a different Hyper-V box, you need to forcefully overwrite the existing box:

$ vagrant box add cdkv2 new-hyper-v-box.img

When the vagrant-registration plugin is used in interactive mode in the Cygwin Bash terminal, the entered password is visible in the standard input. The following warning will be printed:

Error! Your console doesn't support hiding input. We'll ask for
input again below, but we WILL NOT be able to hide input. If this
is a problem for you, ctrl-C to exit and fix your stdin.

The /usr/bin/docker wrapper on Red Hat Enterprise Linux 7 overwrites the DOCKER_CERT_PATH environment variable, which means that the Docker client does not work properly with the Docker service provided by the Container Development Environment. To work around this issue, use directly the docker-current command.

If the vagrant up command is run under the root user, the vagrant-sshfs plugin fails to synchronize the user’s home directory (/root) because the /root/ directory in the Container Development Environment is not empty, and thus SSHFS refuses to use it. To work around this issue use Vagrant as a regular, non-root user.

On Red Hat Enterprise Linux 7.2, the vagrant destroy command does not properly delete the virtually machine storage image. To work around this libvirt bug, you need to change the ownership of the image file and perform several steps using the virsh command.