Chapter 3. Starting and configuring the Single-node OpenShift Cluster for the Fabric8 Launcher tool
This chapter contains instructions for starting the Single-node OpenShift Cluster and configuring it to execute the Fabric8 Launcher tool.
Starting your Single-node OpenShift Cluster can trigger a download of large virtual machines or Linux container images. This can take a long time. Subsequent startups are expected to be shorter as long as the virtual machines and Linux container images remain cached.
Because a Single-node OpenShift Cluster is intended for development purposes, it uses HTTPS for the web console and only provides a self-signed certificate. If your browser prevents you from accessing the page due to an SSL error, you must allow your browser to bypass SSL security policies for the Single-node OpenShift Cluster URL to use it. The screenshot below shows the warning message in the Google Chrome browser.

Prerequisites
Procedure
Start the Single-node OpenShift Cluster with the default virtual machine driver:
NoteDepending on your operating system, virtual machine driver, and the number of boosters you run, the memory allocated Single-node OpenShift Cluster can be insufficient. In this case, increase the memory allocation.
$ minishift start --memory=4096 ... OpenShift server started. The server is accessible via web console at: https://192.168.42.152:8443Alternatively, specify a virtual machine driver other than the default using the
--vm-driverflag:$ minishift start --memory=4096 --vm-driver=virtualbox
Depending on your system configuration, it is possible that you must manually specify an alternative virtual machine driver. You must have virtual machine software, such as VirtualBox, installed before you specify it.
NoteOn macOS, the default virtual machine driver,
xhyve, can be unreliable. If you experience issues, specifyingVirtualBoxis a reliable alternative.Open the Single-node OpenShift Cluster Web console.
$ minishift console
Alternatively, use the URL provided in the log information.
-
Log in using the
developerusername and an arbitrary password. Optionally, delete the preconfigured project:
- Next to the project name, click the three-dot menu icon.
Select Delete Project.


Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.