2

As much as I've looked, I can't find the hardware requirements for running minishift. Nothing mentioned in the Container Development Kit documentation, and the OpenShift documentation only mentions hardware requirements for production deployments.

I've been following RedHat's advice on running their Container Development Kit with nested KVM.

https://developers.redhat.com/blog/2018/02/13/red-hat-cdk-nested-kvm/

I may be pushing the limits. On a MacBook Air with 4x1.7GHz & 8GB RAM I’m running Fedora 27. Gave 6GB RAM & 2 cores to the RHEL Server and starting Minishift saw that it was giving 2 cores and 4GB RAM to VM. It took about 30 minutes to download and extract the 4 docker images. Things got progressively worse from there.

I’m trialing OpenShift Online. Would I run into a world of pain using Minishift directly on Fedora?

rayascott
  • 1,012
  • 9
  • 9

1 Answers1

3

You would be better of running Minishift directly on Fedora 27 with KVM. Personally I use Minishift on Fedora 27. Using nested virtualisation will not give optimum performance as Minishift creates another VM to provision the OpenShift. So I will not recommend using nested virtualisation for Minishift. With the default settings i.e. 4GB RAM, 2 cores and 20GB disk you should be able to run few simple micro services on it. The resource requirement comes from the application you are trying to run on top of it. So if you are running an application which needs a lot of resources then you need to increase the resources to Minishift.

Once you know how much resources are fine for your application, you should save your configurations using "minishift config set" command. It will persist the settings across start/delete.

  • Thank you for mentioning the config set command. I'm new to OpenShift and wasn't aware of that feature. While I do understand that what you end up implementing on Minishift will determine overall hardware requirements, I was curious to know what the baseline "Hello World" requirements are. Is 20GB of space a Minishift default? I guess that's the virtual size of the VM disk, that grows if and when required? How much memory do you run it with? I'll have to experiment more. – rayascott Feb 16 '18 at 12:28
  • For Helloworld experience 2GB RAM , 2 CPU cores is more than enough. The default disk size i.e. 20GB is mostly used for storing docker images. So unless you have very big docker images , 20GB should be enough for you. The disk size can not be increased unless you delete the minishift instance and recreate it. That restriction comes from the hypervisors. You can create an instance of higher size by using "--disk-size" in "minishift start". – Lalatendu Mohanty Feb 17 '18 at 12:11
  • I'm sure you can modify the minishift VM size with virsh. It's just another KVM VM. But that's not needed for now. Thanks for your advice. – rayascott Feb 19 '18 at 10:25