Menu Close

Release Notes and Known Issues

Red Hat Container Development Kit 3.7

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

Red Hat Developer Group Documentation Team

Abstract

This document lists and briefly describes new and improved features of Red Hat Container Development Kit 3.7. 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 provides 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.
  • Container Development Kit is available for the Microsoft Windows, macOS, and Linux operating systems, thus allowing developers to use their preferred 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 3.7 product.

2.1. Component Versions

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

Table 2.1. Container Development Kit, Component Versions

ComponentVersion

Docker

1.13.1

Docker API

1.26

Kubernetes

1.11.0

OpenShift Container Platform

3.11.43

2.2. VirtualBox Compatibility

Red Hat Container Development Kit 3.7 has been tested with VirtualBox 5.2.12 and higher, but is known to not work correctly with VirtualBox 5.1.11 or older. Ensure that you have VirtualBox 5.1.12 or higher if you intend to use VirtualBox as your virtualization provider. VirtualBox 5.2.12 is recommended.

2.3. New Features

This section highlights some of the new features offered by Red Hat Container Development Kit 3.7. The new version also contains a number of bug fixes.

Red Hat Container Development Kit 3.7 contains the Minishift tool, a Red Hat Enterprise Linux 7 ISO, and the oc (OpenShift client) binary for interacting with OpenShift Container Platform.

2.3.1. Minishift

Red Hat Container Development Kit 3.7 is based on Minishift, a command line tool to provision OpenShift locally for application developers. It supports all native hypervisors and some additional ones:

macOS
Linux
Windows

2.3.2. Technology Previews

Support for these features falls under the Technology Preview Features Support Scope.

  • Container Development Kit now supports displaying a status icon in the system tray on Microsoft Windows and macOS. Users can start, check status, and stop the Container Development Kit instance through the system tray.

    By default, the system tray icon is automatically started when running minishift start. To disable the auto-start behaviour, use the following command:

    $ minishift config set auto-start-tray false

    For more information, see CDK System Tray.

2.3.3. Usability Improvements

  • Container Development Kit now includes a time-zone feature, which automatically sets the time zone of the Container Development Environment virtual machine to the same time zone as on the host system. Users can control the feature using the new timezone sub-command:

    $ minishift timezone --set <valid_time_zone>

    For more information, see Timezone Setup.

Chapter 3. Known Issues

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

3.1. General Issues

Issues affecting all supported platforms.

3.1.1. Check for requested OpenShift version fails

The pre-flight check used to verify the requested OpenShift version fails when running minishift start. This is due to deprecated support for the Docker v1 API which is used to verify the requested OpenShift version. For more information, see Deprecation of Docker v1 Content.

To work around this issue, run the following command:

$ minishift config set skip-check-openshift-release true

3.1.2. Building FUSE templates with registry.redhat.io streams fails

When you attempt to build a FUSE template, it fails because the template specifies that images are to be pulled from registry.redhat.io, and credentials for the registry are not included in the myproject OpenShift namespace used by Container Development Kit. This works as expected in the openshift namespace.

3.1.3. xPaaS addon causes start failure

When running minishift start and the xPaaS addon is applied before the API server becomes responsive, the process fails with the following error message:

Error during post cluster up configuration: Error executing command 'oc apply -f v#{OPENSHIFT_VERSION}/xpaas-streams -n openshift'.

To work around this issue, re-apply the addon:

$ minishift addons apply xpaas

3.2. Issues on macOS

This section describes CDK issues that affect users on a macOS host.

3.2.1. OpenShift web console does not work with older versions of Safari

minishift console does not work on older versions of the Safari web browser such as version 10.1.2 (12603.3.8). Attempting to access the web console results in the following error:

Error unable to load details about the server

Retry after updating Safari to the latest version or use the Firefox or Chrome web browsers for this. Safari version 11.0.3 (13604.5.6) has been tested and works with the OpenShift web console. You can use minishift console --url to get the web console URL.

3.3. Issues on Microsoft Windows

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

3.3.1. System tray icon does not reflect profile status

The system tray icon (introduced as a Technology Preview feature in Container Development Kit 3.7) does not show profile status. There is no workaround available.

3.3.2. Default Switch does not work as expected with static IP

The experimental static IP feature is not possible with the Default Switch provided by Windows. The minishift virtual machine will receive an IP address, but network traffic will not be able to pass through it.

See Assign IP Address to Hyper-V for more information about how to assign a static IP address to the minishift VM on Windows.

3.3.3. Windows Command Prompt and PowerShell improperly parse JSON patches for the minishift openshift config set command

Windows Command Prompt and PowerShell have problems with parsing JSON into the minishift openshift config set command. Special attention is required when using this command on Windows.

The workaround for Windows Command Prompt environments is to escape the quotes so that the JSON content is correctly parsed:

C:\Users\CDK> minishift.exe openshift config set --patch "{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}"

The workaround for Windows PowerShell environments is to use a variable to store the JSON content:

PS C:\Users\CDK> $json='{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}'
PS C:\Users\CDK> echo $json
{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}
PS C:\Users\CDK> minishift.exe openshift config set --patch $json
Patching OpenShift configuration /var/lib/origin/openshift.local.config/master/master-config.yaml with {"routingConfig": {"subdomain": "192.168.99.101.nip.io"}}

3.3.4. minishift openshift config set --patch may fail on some Windows 7 and 10 hosts

The reason for this failure is currently unknown.

Workaround: Configure the OpenShift cluster from inside of the provisioned VM using minishift ssh:

C:\Users\CDK> minishift.exe ssh
[docker@minishift ~]$ docker exec -t origin /usr/bin/openshift ex config patch /var/lib/origin/openshift.local.config/master/master-config.yaml --patch='<json-to-be-applied-to-the-cluster>'

Chapter 4. Additional Resources

Legal Notice

Copyright © 2019 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.