Red Hat Training

A Red Hat training course is available for Red Hat Container Development Kit

Chapter 3. Known Issues

This section describes issues that users of Red Hat Container Development Kit 2.1 may encounter, as well as possible workarounds for these issues.

3.1. General Issues

Issues affecting all supported platforms.

3.1.1. Vagrantfiles That Set Up SSHFS Cannot Be Used with JBoss Developer Studio

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/.

3.1.2. No support for network proxies

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

3.1.3. DNS service provided by xip.io only works with an Internet connection

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

3.2. Issues on Microsoft Windows

This section describes issues that only affect users using Container Development Kit on a Microsoft Windows host system.

3.2.1. Hyper-V Vagrant Box Cannot Be Removed

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

3.2.2. vagrant-registration Plugin on Cygwin Bash Does Not Hide Password

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.

3.3. Issues on Red Hat Enterprise Linux

This section describes issues that only affect users using Container Development Kit on a Red Hat Enterprise Linux host system.

3.3.1. The docker command Cannot Communicate with Container Development Kit

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.

3.3.2. SSHFS Does Not Work when Vagrant Used under Root User

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.