Release Notes and Known Issues

The Container Development Environment provided by Red Hat Container Development Kit 2.2 now supports connecting to the Internet through proxy servers — both HTTP and HTTPS configurations. This support is available to all services running within the Container Development Environment, including Openshift Enterprise, Kubernetes, and Docker.

Vagrantfiles distributed as a part of the Red Hat Container Tools ZIP file and used for initializing the Container Development Environment Vagrant box have been unified to work with all supported hypervisors. This means that the directory structure now looks as follows:

~]$ tree cdk/
cdk/
├── components
│   └── rhel
│       ├── misc
│       │   └── rhel-k8s-singlenode-setup
│       │       ├── README.rst
│       │       └── Vagrantfile
│       └── rhel-ose
│           ├── README.rst
│           └── Vagrantfile
├── LICENSE
├── plugins
│   ├── vagrant-registration-README.md
│   ├── vagrant-registration-1.2.3.gem
│   ├── vagrant-service-manager-README.adoc
│   ├── vagrant-service-manager-1.3.2.gem
│   ├── vagrant-sshfs-README.md
│   └── vagrant-sshfs-1.2.0.gem
└── README.md

6 directories, 14 files

Previously, the Vagrant-sshfs plugin, which enables seamless synchronization of directories between the user’s host system and the Container Development Environment, did not work well with Red Hat JBoss Developer Studio. As a consequence, SSHFS could not be used when launching the Container Development Environment from JBoss Developer Studio, and a special set of Vagrantfiles had to be provided for starting the Container Development Environment with SSHFS support. The problem has been fixed, and it is now possible to use SSHFS with JBoss Developer Studio, and there is no need for separate Vagrantfiles.

Client binaries for the user’s host system, which can be used to interact with services running inside the Container Development Environment, can now be installed using the Vagrant-service-manager' plugin. Installation is supported for the `oc, kubectl, and docker binaries, which can be used to work with the OpenShift Enterprise, Kubernetes, and Docker services respectively.

Previously, it was not possible to resubmit Red Hat Subscription credentials during the vagrant up phase of Container Development Kit installation in case a mistake has been made while entering the credentials. The Vagrant-registration plugin has been modified to ask for correct credentials three times, thus improving user experience.

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

After signing up for a Red Hat Developers account, you must wait approximately fifteen minutes to allow the new account information to propagate to the Red Hat Subscription Management system before the Container Development Environment can be registered.

The nodejs-4-rhel7 Docker-formatted container image, which is available from the Red Hat Atomic Registry, does not work when the Container Development Environment is connected to the Internet through a proxy server.

To enable automatic registration of the Container Development Environment Vagrant box, credentials for to Red Hat Subscription must be defined in the Vagrantfiles that are supplied in the Red Hat Container Tools ZIP file. Credentials defined in the user’s global Vagrantfile in /home/<username>/.vagrant.d/ are ignored by the vagrant-registration plugin.

An insecure certificate causes an error when using oc login. Use the --insecure-skip-tls-verify=true option with the oc login command to prevent the warning about insecure connection.

When using the Container Development Environment behind a proxy server, the vagrant reload command does not work properly, which results in OpenShift applications not loading. To avoid this issue, halt and restart your Container Development Environment Vagrant box using the vagrant halt and vagrant start commands.

When the registration of the Container Development Environment to Red Hat Subscription fails, the user is shown the following error message:

==> default: WARNING: manager, skip, unregister_on_halt, username, password, serverurl, baseurl, org, environment, name, auto_attach, activationkey, servicelevel, release, force, type, ca_cert, pools
Information required to complete this request is missing from your account. Please log into https://www.redhat.com/wapps/login to complete account creation.

The URL suggested by the error message is invalid.

If you encounter this problem, either register from within the Container Development Environment Vagrant box, or destroy the Vagrant box and rerun the vagrant up command.

Using the --path option when installing the oc, kubectl, or docker binaries with the install-cli command of the vagrant-service-manager plugin does not work as expected. The following error is shown:

The system cannot find the path specified.

When using the Container Development Environment connected to the Internet through a proxy server that only has a self-signed TSL certificate, the registration to Red Hat Subscription fails. To work around this problem, edit the etc/rhsm.conf configuration file within the Container Development Environment to contain the following line and try to register again:

# Set to 1 to disable certificate validation:
insecure = 1

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.

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.