Chapter 3. Known Issues

Using cached images created by minishift start --image-caching can sometimes be slower than downloading those images.

The minishift start --metrics command fails to properly deploy metrics container images due to a problem with version tags on these images. The workaround is to use --ocp-tag v3.6. Despite using the same OCP version, this allows minishift start to pull metrics images properly.

The minishift start --logging command fails to properly deploy logging container images due to a problem with version tags on these images. The workaround is to use --ocp-tag v3.6. Despite using the same OCP version, this allows minishift start to pull logging images properly.

The directory set in the MINISHIFT_HOME environment variable is rewritten whenever the minishift setup-cdk command is executed. Do not set it to a directory that contains data that cannot be discarded, such as your home directory. The minishift command displays a warning about the deletion of the directory.

Support for --ocp-tag v3.6.0 was not originally available with Container Development Kit 3.1, so no version of OpenShift later than 3.5 could be used with CDK 3.1. For Container Development Kit 3.1.1, the default version of OpenShift is 3.6.173.0.5, so --ocp-tag is not needed to get OpenShift v3.6.

The --ocp-tag flag for the minishift start command does not support the "latest" tag. Workaround: If you want to use any OCP image other than the default, you need to find the version number of the specific image you want and select that version. You can find the image using --ocp-tag help. The tag will be in the format: "v.X.Y.Z". Currently, no version later than the default 3.6.173.0.5 is available.

The minishift openshift service outputs the word namsepace instead of namespace. This causes no functional problem.

When you exit from minishift ssh after executing a command that fails, Minishift will print an improper error message. Workaround: Ignore the error message, nothing bad happened. Here is an example:

minishift ssh
mistake
exit

~]$ minishift ssh
Last login: Tue Apr  4 09:24:43 2017 from 192.168.42.1
~]$ mistake
-bash: mistake: command not found
~]$ exit
logout
E0404 09:31:11.723209    5180 ssh.go:38] Cannot establish SSH connection to the VM:  exit status 127

On a fresh Container Development Kit 3.1.1 setup, when you execute minishift version the .minishift directory is created and default addons are automatically installed. After that, when you run the minishift setup-cdk command, you are warned the .minishift directory exists and that all data will be deleted, then asked if you want to continue. Workaround: Always type y to continue. The addons will be properly installed.

Output from the minishift start -h command improperly identifies the URL for finding available OpenShift tags as follows:

Check the available tags in https://access.redhat.com/containers/#/registry.access.redhat.com/openshift3/ose/images (default "v3.6.173.0.5")

Check the available tags in https://access.redhat.com/containers/#/registry.access.redhat.com/openshift3/ose/images (default "v3.6.173.0.5")

The proper URL is:

https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/openshift3/ose

https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/openshift3/ose

Microsoft Windows CMD and PowerShell have problems with parsing JSON into minishift openshift config set command. Special attention needed from user when using this command on Windows. The workaround is to use exact and verified example commands as mentioned on github.

minishift openshift config set --patch '{"corsAllowedOrigins": [".*"]}'

C:\Users\CDK> minishift openshift config set --patch '{"corsAllowedOrigins": [".*"]}'
The specified patch need to be valid JSON.

The workaround for Microsoft Windows CMD environments is to escape the quotes so that the JSON is correctly parsed:

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

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

For Powershell v2 environments on Microsoft Windows, the workaround is to use a variable to store the JSON code:

$json='{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}'
echo $jason
minishift.exe openshift config set --patch $jason

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

Using the Gow (GNU on Windows) utility installer to install the SSH utility causes the following error message when SSH is invoked to start Container Development Kit virtual machine with VirtualBox on Windows 7:

0907 09:49:02.791900    3456 start.go:282] Error starting the VM: Error
creating the VM. Error creating machine: Error in driver during machine
creation: Too many retries waiting for SSH to be available.  Last error:
Maximum number of retries (60) exceeded. Retrying.

0907 09:49:02.791900    3456 start.go:282] Error starting the VM: Error
creating the VM. Error creating machine: Error in driver during machine
creation: Too many retries waiting for SSH to be available.  Last error:
Maximum number of retries (60) exceeded. Retrying.

Despite this message, the VM started successfully.