minishift: Could not set oc CLI context for 'minishift' profile; specified path to the kube config does not exist

General information

  • Minishift version: v1.34.0+f5db7cb
  • OS: Windows 10
  • Hypervisor: VirtualBox

Steps to reproduce

I am an OpenShift and minishift newbie and learning OpenShift. Am getting the following error while starting minishift: Could not set oc CLI context for 'minishift' profile: Error during setting 'minishift' as active profile: The specified path to the kube config 'C:\Users\me.myself\.minishift\machines\minishift_kubeconfig' does not exist

although it seems minishift and oc cluster both are up, and I am able to access the console as well.

$ minishift status
Minishift:  Running
Profile:    minishift
OpenShift:  Running (openshift v3.11.0+7f5d53b-195)
DiskUsage:  15% of 19G (Mounted On: /mnt/sda1)
CacheUsage: 491.9 MB (used by oc binary, ISO or cached images)

But when I try to deploy an app via CLI I get an error:

$ oc new-app https://github.com/sclorg/nodejs-ex -l name=myapp
error: Missing or incomplete configuration info.  Please login or point to an existing, complete config file:

  1. Via the command-line flag --config
  2. Via the KUBECONFIG environment variable
  3. In your home directory as ~/.kube/config

To view or setup config directly use the 'config' command.

Unable to deploy anything from console also, (was trying tod eploy a Jenkins pipeline sample app from catalog), getting following error:

--> Scaling mongodb-1 to 1
--
  | error: update acceptor rejected mongodb-1: pods for rc 'first-test/mongodb-1' took longer than 600 seconds to become available

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 25

Most upvoted comments

Hi, I solved the problem for me the following way: I delete minishift version 1.34 and installed minishift version 1.33. (this has probably nothing to do with me getting this working) And I also did this: minishift config set openshift-version v3.10.0 then minishift delete and minishift start

So, my assumption is this: Minishift has issues with Openshift version 3.11 and none with Openshift version 3.10

Solved here using: $ minishift delete --force $ rm -rf ~/.minishift $ minishift setup-cdk $ minishift config set vm-driver virtualbox $ minishift start

I am experiencing the same problem. I want to do your workaround but this step does not work for me … $ minishift setup-cdk Error: unknown command “setup-cdk” for “minishift” Run ‘minishift --help’ for usage. unknown command “setup-cdk” for “minishift”

Is this possibly a typo?