minishift: OpenShift fails to start when Minishift instance has changed IP address
Version of Minishift : 1.0.0.Beta2
This error is not resorted the first time you create the VM but if you have stopped & restarted minishift
minishift start --openshift-version=v1.4.1 --memory=4000 --vm-driver=virtualbox --iso-url=https://github.com/minishift/minishift-centos-iso/releases/download/v1.0.0-beta.1/minishift-centos.iso --docker-env=[storage-driver=devicemapper]
Starting local OpenShift instance using 'virtualbox' hypervisor...
Provisioning OpenShift via '/Users/chmoulli/.minishift/cache/oc/v1.4.1/oc [cluster up --use-existing-config --host-config-dir /var/lib/minishift/openshift.local.config --host-data-dir /var/lib/minishift/hostdata]'
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v1.4.1 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
Using 192.168.99.100 as the server IP
-- Starting OpenShift container ... FAIL
Error: Docker run error rc=2
Details:
Image: openshift/origin:v1.4.1
Entrypoint: [/bin/bash]
Command: [-c for name in 192.168.99.100 minishift; do ls /var/lib/origin/openshift.local.config/node-$name &> /dev/null && echo $name && break; done]
E0130 10:23:41.050352 2473 start.go:246] Error starting 'cluster up': exit status 1
About this issue
- Original URL
- State: open
- Created 7 years ago
- Reactions: 2
- Comments: 35 (26 by maintainers)
@LalatenduMohanty remove the VM is a no go for me to promote minishift for windows using Hyper-V. I second @gbraad into there needs to be an easier workaround. Pulling down GBs of images every time you destroy the VM is one of the biggest pushes backs that people will have towards minishift, so until a solution to save containers on the host is not there, we can not delete the VMs with such a happiness.
Just think what you’re proposing. I am a developer. I’m working connected to my wired connection in my home office, I then decided to work from my sitting room, I connect to my wifi instead and I need to pull down some GBs of images again? That is “insane” and excuse me for saying this.
Please have a look at https://github.com/ahilbig/docker-machine-ipconfig . It’s a workaround because the solution for assigning a static IP is not finally fixed in docker-machine - just install the script and call ‘minishift-ipconfig static’ after starting the cluster first time. Tested on Cygwin.
This error is basically because the ip of the vm has changed since it was created. It’s a known issue of oc cluster.
cc/ @hferentschik @csrwng
I have retested and now the iso has been downloaded correctly
Maybe, an additional test should be included within the code to avoid to ssh within the VM if if the iso file hasn’t been downloaded completely. The question will be : how can we figure out if the iso file is 100% downloaded