Release Notes and Known Issues


Red Hat Container Development Kit 2.4

Highlighted features and identified problems in Red Hat Container Development Kit 2.4

Robert Krátký

Red Hat Developer Group Documentation Team

Abstract

This document lists and briefly describes new and improved features of Red Hat Container Development Kit 2.4. It also contains information about potential problems you may encounter while using the software. Where possible, workarounds are described for identified issues.

Chapter 1. Introducing Red Hat Container Development Kit

Red Hat Container Development Kit is a platform for developing containerized applications — it is a set of tools that enables developers to quickly and easily set up an environment for developing and testing containerized applications on the Red Hat Enterprise Linux platform.

  • Container Development Kit provides a personal Container Development Environment you can install on your own laptop, desktop, or server system. The Container Development Environment is provided in the form of a Red Hat Enterprise Linux virtual machine. The Container Development Environment itself can also be installed in a virtual machine.
  • Container Development Kit includes the same container-development and run-time tools used to create and deploy containers for large data centers.
  • Container Development Kit offers an easy installation method that results in virtual machines created from pre-configured Vagrant boxes and Vagrantfiles running on your local system.
  • Container Development Kit is available for Microsoft Windows, Mac OS X, and Linux operating systems, thus allowing developers to use their favorite platform while producing applications ready to be deployed in the Red Hat Enterprise Linux ecosystem.

Container Development Kit is a part of the Red Hat Developers program, which provides tools, resources, and support for developers who wish to utilize Red Hat solutions and products to create applications, both locally and in the cloud. For additional information and to register to become a part of the program, visit developers.redhat.com.

1.1. Understanding Container Development Kit Documentation

Chapter 2. Release Notes

This section documents the most important features and bug fixes in the Red Hat Container Development Kit 2.4 product.

2.1. Component Versions

Red Hat Container Development Kit 2.4 is shipped with the following versions of the main components:

Table 2.1. Container Development Kit, Component Versions
ComponentVersion

Docker

1.12.5

Docker API

1.24

Kubernetes

1.4.0

OpenShift Container Platform

3.4

2.2. VirtualBox Compatibility

Red Hat Container Development Kit 2.4 has been tested with VirtualBox 5.0.26 and higher, but it is known to not work correctly with VirtualBox 5.1.x. If you intend to use VirtualBox as your virtualization provider, and you already have VirtualBox 5.1.x installed, downgrade your installation to VirtualBox 5.0.26.

2.3. Vagrant Compatibility Matrix

The Container Development Environment provided by Container Development Kit is delivered in the form of a virtual machine that is administered by Vagrant. Not all versions of Vagrant work correctly with the Container Development Environment on all supported platforms. The following table shows version requirements for Vagrant based on the platform and hypervisor used.

Table 2.2. Vagrant Compatibility Matrix
 

Vagrant version

 

1.7.4

1.8.1

Microsoft Windows with VirtualBox

Microsoft Windows with Hyper-V

macOS with VirtualBox

Red Hat Enterprise Linux with libvirt

2.4. New Features

This section documents changes to Red Hat Container Development Kit 2.4.

2.4.1. Relative Paths Are Now Supported

Relative pathnames are now supported, so the full path does not need to be specified with the --path option. For example, the following should now work:

C:\> mkdir test
C:\> vagrant.exe service-manager install-cli openshift --path test

2.4.2. Updated Openshift Container Platform

Container Development Kit 2.4 now includes OpenShift Container Platform 3.4.0.40.

2.4.3. Red Hat Container Development Kit 3.0 beta now available

Red Hat Container Development Kit is available as Red Hat Container Development Kit 3.0 beta. No technical support is provided for this beta version.

Chapter 3. Known Issues

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

3.1. General Issues

Issues affecting all supported platforms.

3.1.1. Vagrantfile for Individual Users is Ignored When Using a Proxy

A Vagrantfile for a specific user does not use the supplied username and password if configured to use a proxy. The following file created in ~/.vagrant.d/Vagrantfile does not work as expected:

Vagrant.configure(2) do |config|
  config.registration.username = "actual_username"
  config.registration.password = "actual_password"
end

Specifying the username and password by using environment variables has the same result:

~]$ export PROXY="proxy_addr"
~]$ export PROXY_USER="actual_user"
~]$ export PROXY_PASSWORD="actual_password"

The user will be prompted interactively for the username and password in either case.

If no proxy is set, Container Development Kit uses the username and password supplied in ~/.vagrant.d/Vagrantfile.

3.2. Issues on Microsoft Windows

This section describes issues that only affect users on a Microsoft Windows host system.

3.2.1. vagrant service-manager Output Shows Paths With Cygwin Syntax

The output from vagrant service-manager does not follow Microsoft Windows CMD.exe syntax. The path given does not work outside of Cygwin. The following error is shown:

C:\DevelopmentSuite\cdk\componenets\rhel\rhel-ose> mkdir C:\tmp
C:\DevelopmentSuite\cdk\componenets\rhel\rhel-ose> vagrant service-manager install-cli openshift --path C:\tmp

# Binary now available at /cygdrive/c/tmp
# run binary as:
# oc <command>
export PATH=/cygdrive/c/tmp:$PATH

# run following command to configure your shell:
# eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager install-cli openshift --path /cygdrive/c/tmp | tr -d '\r')"

The correct syntax for Microsoft Windows paths includes the drive letter and path available in Microsoft Windows outside of Cygwin, in this case C:\tmp

3.2.2. Using Cygwin Syntax for a Path Causes an Error

The vagrant service-manager install-cli command with --path option does not work when using Cygwin syntax on both Microsoft Windows 7 and 10. The following error is shown:

~] $ vagrant.exe service-manager install-cli openshift --path /cygdrive/c/test
undefined local variable or method `dir_name' for #<VagrantPlugins::ServiceManager::Installer:0x492b130>

To workaround this issue, use the CMD.exe syntax with drive letter for the path, like vagrant.exe service-manager install-cli openshift --path c:/test

Chapter 4. Additional Resources

Legal Notice

Copyright © 2017 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.