CDK workaround for failing OpenShift version check

CDK workaround for failing OpenShift version check

This article contains a workaround for Red Hat Container Development Kit (CDK) suddenly failing to start. If you are getting the message “Checking if requested OpenShift version ‘v3.11.82’ is valid … FAIL,” see the solution below.

Red Hat is ending support for Docker v1 content (v1 API and v1 schema container images) across Red Hat container registries. For more information, see Deprecation of Docker v1 Content.

CDK uses the Docker v1 API to verify the requested OpenShift version. Due to the deprecation of Docker v1 content, this will result in CDK failing to start as shown:

$ minishift start
-- Starting profile 'minishift'
-- Check if deprecated options are used ... OK
-- Checking if https://mirror.openshift.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.11.82' is valid ... FAIL

To work around this issue, run the following command:

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

We are trying to release a bug fix version of CDK 3.7 within two weeks to address this issue.

For more information about Red Hat OpenShift and other related topics, visit: OpenShift, OpenShift Online.

Share