Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Release Notes
This section documents the most important features and bug fixes in the Red Hat Container Development Kit 2.3 product.
2.1. Component Versions Copiar o linkLink copiado para a área de transferência!
Red Hat Container Development Kit 2.3 is shipped with the following versions of the main components:
Component | Version |
---|---|
Docker | 1.10.3 |
Docker API | 1.22 |
Kubernetes | 1.3.0 |
OpenShift Container Platform | 3.3 |
2.2. VirtualBox Compatibility Copiar o linkLink copiado para a área de transferência!
Red Hat Container Development Kit 2.3 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 Copiar o linkLink copiado para a área de transferência!
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.
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 Copiar o linkLink copiado para a área de transferência!
This section highlights some of the new features offered by Red Hat Container Development Kit 2.3. The new version also contains a number of bug fixes.
2.4.1. The install-cli Command of the Vagrant-service-manager Plugin Improved Copiar o linkLink copiado para a área de transferência!
The install-cli
command provided by the Vagrant-service-manager plugin has been improved to offer the possibility to specify both a destination path for the client binaries it installs (using the --path
option) and a specific version of the binaries (using the --cli-version
option).
See the Container Development Kit Getting Started Guide for instructions on how to use these new options:
2.4.2. Proxy Support Improved when Using the Vagrant-service-manager Plugin Copiar o linkLink copiado para a área de transferência!
Previously, it was not possible to install client binaries on the host system using the install-cli
command of the Vagrant-service-manager plugin when behind a proxy. With this update, support has been added for a seamless installation of client binaries for OpenShift Container Platform (oc
) and Docker (docker
) using the install-cli
command of the Vagrant-service-manager plugin even when using Container Development Kit behind a proxy.
See the Red Hat Container Development Kit 2.3 Installation Guide for instructions on how to set up the Container Development Environment for behind a proxy using the Vagrant-service-manager plugin: