Chapter 3. Known issues
This section describes issues that users of Red Hat Container Development Kit 3.17 may encounter, as well as possible workarounds for these issues.
3.1. General Issues
Issues affecting all supported platforms.
3.1.1. The Container Development Kit virtual machine contains docker-1.13.1-161
The Container Development Kit virtual machine contains docker-1.13.1-161
instead of the newer docker-1.13.1-162
. The advisory for docker-1.13.1-162
informed customers of CVE fixes that were previously applied in docker-1.13.1-109
. The included docker-1.13.1-161
package contains these CVE fixes but may be flagged by security scanning tools.
For more information, see the Vulnerability Response article for a runc
regression in docker-1.13.1-108
.
3.1.2. Container Development Kit does not start with VirtualBox 6
When running Container Development Kit with VirtualBox 6, you may encounter the following error message:
Error starting the VM: Error creating the VM. Error with pre-create check: "Virtual Box version 4 or lower will cause a kernel panicif xhyve tries to run. You are running version: 6.0.4r128413\n\n\t Please upgrade to version 5 at https://www.virtualbox.org/wiki/Downloads"
Workaround: run minishift start
with the --vm-driver virtualbox
option.
3.1.3. OpenShift Container Platform cluster times out waiting for response from API server
When starting the cluster via minishift start
, you may encounter the following error message:
Error: timed out waiting for the condition
Cause: This issue is caused by oc cluster up
, which is used by Container Development Kit to start the OpenShift Container Platform cluster. The underlying cause of the timeout is unknown.
Workaround: Delete the existing Container Development Kit virtual machine, then retry starting the cluster using the following commands:
$ minishift delete $ minishift start
This issue may be persistent on your hardware. In this case, the only known workaround is to use a more powerful host machine.
3.1.4. 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.5. 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>'
Additional resources
- See the Container Development Kit Getting Started Guide for an overview of Container Development Kit features and an introduction to the use of the Docker service and OpenShift Container Platform.
- Report issues with Red Hat Container Development Kit or request new features using the CDK project at https://issues.jboss.org/projects/CDK.