Minishift on HyperV

Although I would not consider myself as a heavy user of Windows, I believe I need to try to meet the challenge of supporting those running Linux, MacOS, and Windows.
I recently ran into an issue running Minishift on Windows 10 and Hyper-V.  I suspect regular users of both of these technologies might already be aware of what tripped me up but I thought I would document it here just in case someone needs it.  In case you're not aware of it, Minishift is a very nice project that allows a developer to easily run OpenShift, also known as OCP or OpenShift Container Platform, on a desktop computer.
Overall, I had a nice experience installing Minishift on a Windows 10 computer running HyperV but once I stopped and restarted Minishift, and had a new ip address address assigned to the VM, the instance would no longer start.  
Now if you're doing any Docker development on your computer and you move around a good bit or perhaps you're on and off a VPN, you probably know that virtualization and containerization does not always take too kindly to changing ip addresses and subnets.  Certainly, deleting and reinstalling is an option but that can be very costly depending on what's going on with your project.
I may have missed it in the Minishift setup guide, but I used the default setting of "dynamic" for the MAC address on the VM.  

I think the MAC address changed (I have read that HyperV does this if it believes it's necessary although I did not find what events might cause such a belief) and therefore I would assume that the DHCP server issued a new ip address and possibly caused my issue.
Unfortunately it's speculation on my part at this time but I have changed the configuration to use a static MAC address for the minishift HyperV VM.  I will try to update this entry should I learn more.

In the meantime, happy computing,
Carl

Comments

Post a Comment

Popular posts from this blog

ClassCastException: JAXB

Image
A particular Java application I co-developed leverages both SOAP/WSDL and REST web services.  We use maven to manage the build process of this application which has been in production for a few years now.  It's been around long enough to have moved from Java 5 to Java 6 and now Java 7 (with limited testing using Java 8).  We have also had the experience of initially including JAXB jar files with our application and dealing with the "endorsed" directory because JAXB versions were a bit of a moving target for a while. Now that JAXB is neatly included with Java as it should be so we no longer include it.  I thought all of this was behind us (and unfortunately somewhat forgotten) until recently when we added Jersey 1.17 to the application to call some newer REST services. When trying to connect to the server, my stack trace included this: Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.internal.bind.api
Read more

Parallel to Lincoln's angry letters never sent concept...

With all that I read, hear, and see these days about folks (not excluding yours truly) expressing themselves, I sometimes wonder about President Lincoln's idea of writing but not sending letters .  For better or worse, there is certainly a sharp contrast between that and typical use of today's communication. I was not necessarily thinking of opinions, emotions, and perspectives although I do see the wisdom in the Lincoln's method of dealing with such issues. My issue, at least this time, was being stuck with a particular problem using a technology which is not part of my regularly used skillset.  The technology itself is irrelevant to my point so I won't name it here. I had struggled with a solution after a bit of reading the documentation, searching for and modifying some similar examples, and experimentation.  The time I had put in was actually very little because I was simultaneously working on other parts of the solution.  That's another way of saying I wa
Read more