このコンテンツは選択した言語では利用できません。
Chapter 1. Getting Started with Container Development Kit
This section contains information about setting up, installing, updating and uninstalling Container Development Kit.
1.1. Introducing Red Hat Container Development Kit リンクのコピーリンクがクリップボードにコピーされました!
Red Hat Container Development Kit is a platform for developing containerized applications on a single, personal system. It enables developers to quickly and easily set up an environment for developing and testing containerized applications on the Red Hat Enterprise Linux platform.
CDK:
- Provides a personal Container Development Environment you can install on your own laptop, desktop, or server system. The Container Development Environment is provided in the form of a Red Hat Enterprise Linux virtual machine. The Container Development Environment itself can also be installed in a virtual machine.
- Includes the same container-development and runtime tools used to create and deploy containers for large data centers.
- CDK version 3 offers an easy installation method based on the minishift tool.
- Runs on Microsoft Windows, macOS, and Linux operating systems as a Linux virtual machine, thus allowing developers to use their favorite platform while producing applications ready to be deployed in the Red Hat Enterprise Linux ecosystem.
CDK is a part of the Red Hat Developers program, which provides tools, resources, and support for developers who wish to utilize Red Hat solutions and products to create applications, both locally and in the cloud. For additional information and to register to become a part of the program, visit developers.redhat.com.
1.1.1. Additional Information リンクのコピーリンクがクリップボードにコピーされました!
Refer to the following documents for further information:
- See Red Hat Container Development Kit 3.2 Release Notes and Known Issues for information about the current release of the product as well as a list of known problems that users may encounter when using it.
- See Container Development Kit Getting Started Guide for instructions on how to install and start using the Container Development Environment to develop Red Hat Enterprise Linux-based containers using tools and services such as OpenShift Container Platform, Docker, Eclipse, and various command-line tools.
To report issues, refer to the following:
- For Red Hat Container Development Kit issues or to request new CDK features, refer to the CDK Project.
- For issues with Red Hat Container Development Kit documentation or to request new documentation, refer to CDK Project Documentation.
1.2. Preparing to Install Container Development Kit リンクのコピーリンクがクリップボードにコピーされました!
1.2.1. Overview リンクのコピーリンクがクリップボードにコピーされました!
Container Development Kit 3.2 is based on Minishift 1.7.0. Using a single executable file, the minishift command deploys CDK as a Red Hat Enterprise Linux virtual machine, running OpenShift (which includes Kubernetes, the Docker service, and other container development and deployment software).
The CDK setup procedure can, and should, be run as a regular user that has special permission to launch virtual machines. In the procedure, you will see how to assign that permission, along with ways to configure your hypervisor and command shell to start and effectively interact with CDK.
CDK version 2.x was based on Vagrant. Because of the completely different deployment and management methods, there is no upgrade path from CDK 2.x to CDK 3.x versions. You need to do a fresh setup.
The following section describes how to install CDK and the required dependencies.
1.2.2. Prerequisites リンクのコピーリンクがクリップボードにコピーされました!
CDK requires a hypervisor to start the virtual machine on which the OpenShift cluster is provisioned. Verify that the hypervisor of your choice is installed and enabled on your system before you set up CDK. Once the hypervisor is up and running, additional setup is required for CDK to work with that hypervisor (as described in the coming setup procedure).
Depending on your host operating system, you have the choice of the following hypervisors:
- macOS
- xhyve (default)
- VirtualBox
- Red Hat Enterprise Linux
- KVM (default)
- VirtualBox
- Windows
- Hyper-V (default)
- VirtualBox
Refer to the documentation for each hypervisor to determine the hardware and operating system versions needed to run that hypervisor.
1.2.3. Understanding CDK Installation リンクのコピーリンクがクリップボードにコピーされました!
These are the basic steps for setting up CDK on your personal laptop or desktop system:
- Set up your virtualization environment
- Download CDK software for your operating system from the Red Hat Container Development Kit Download Page
- Set up CDK
- Start CDK
- Configure CDK so you can use it efficiently
1.3. CDK Installation リンクのコピーリンクがクリップボードにコピーされました!
1.3.1. Installing CDK リンクのコピーリンクがクリップボードにコピーされました!
The following steps describe how to prepare your virtualization environment (hypervisor) for CDK, download CDK software, set up CDK, and start using it.
1.3.2. Step 1: Set up your virtualization environment リンクのコピーリンクがクリップボードにコピーされました!
Follow the appropriate procedure to set up virtualization for your particular operating system and hypervisor. CDK uses Docker Machine and its driver plug-in architecture to provide a consistent way to manage the OpenShift VM.
Some hypervisors require manual installation of the driver plug-in. CDK embeds VirtualBox drivers so no additional steps are required to configure the driver. However, a minishift command option (--vm-driver virtualbox) will be required later to identify VirtualBox to CDK.
1.3.2.1. Set up hypervisor on Red Hat Enterprise Linux リンクのコピーリンクがクリップボードにコピーされました!
Choose between KVM (default) and VirtualBox for your hypervisor. Manual driver setup is required for KVM. The driver is automatically configured if you install VirtualBox. However, a minishift command will be required later to identify VirtualBox to CDK.
On Red Hat Enterprise Linux with KVM virtualization: CDK is currently tested against docker-machine-driver-kvm version 0.7.0. Follow these steps to install the KVM driver and configure your user account to use the libvirtd service.
As root, install the KVM binary and make it executable as follows:
curl -L https://github.com/dhiltgen/docker-machine-kvm/releases/download/v0.7.0/docker-machine-driver-kvm -o /usr/local/bin/docker-machine-driver-kvm chmod +x /usr/local/bin/docker-machine-driver-kvm
# curl -L https://github.com/dhiltgen/docker-machine-kvm/releases/download/v0.7.0/docker-machine-driver-kvm -o /usr/local/bin/docker-machine-driver-kvm # chmod +x /usr/local/bin/docker-machine-driver-kvmCopy to Clipboard Copied! Toggle word wrap Toggle overflow For more information, see the GitHub documentation of the Docker Machine KVM driver.
As root, install libvirt and qemu-kvm on your system and add yourself to the libvirt group:
yum install libvirt qemu-kvm usermod -a -G libvirt <username>
# yum install libvirt qemu-kvm # usermod -a -G libvirt <username>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Update your current user session to apply the group change:
newgrp libvirt
$ newgrp libvirtCopy to Clipboard Copied! Toggle word wrap Toggle overflow Start the libvirtd service as root:
systemctl start libvirtd systemctl enable libvirtd
# systemctl start libvirtd # systemctl enable libvirtdCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.3.2.2. Set up hypervisor on macOS リンクのコピーリンクがクリップボードにコピーされました!
Choose between xhyve (default) and VirtualBox for your hypervisor. Manual driver setup is required for xhyve. The driver is automatically configured if you install VirtualBox. However, a minishift command option (--vm-driver virtualbox) will be required later to identify VirtualBox to CDK.
On macOS with xhyve virtualization:
CDK on macOS with xhyve virtualization is currently tested against docker-machine-driver-xhyve version 0.3.3. To manually install the xhyve driver, you need to download and install the docker-machine-driver-xhyve binary and place it in a directory which is on your PATH environment variable. The directory /usr/local/bin is most likely a good choice, since it is the default installation directory for Docker Machine binaries.
The following steps explain the installation of the docker-machine-driver-xhyve binary to the /usr/local/bin/ directory:
Download the
docker-machine-driver-xhyvebinary using:sudo curl -L https://github.com/zchee/docker-machine-driver-xhyve/releases/download/v0.3.3/docker-machine-driver-xhyve -o /usr/local/bin/docker-machine-driver-xhyve
$ sudo curl -L https://github.com/zchee/docker-machine-driver-xhyve/releases/download/v0.3.3/docker-machine-driver-xhyve -o /usr/local/bin/docker-machine-driver-xhyveCopy to Clipboard Copied! Toggle word wrap Toggle overflow Enable root access for the
docker-machine-driver-xhyvebinary and add it to the default wheel group:sudo chown root:wheel /usr/local/bin/docker-machine-driver-xhyve
$ sudo chown root:wheel /usr/local/bin/docker-machine-driver-xhyveCopy to Clipboard Copied! Toggle word wrap Toggle overflow Set owner User ID (SUID) for the binary as follows:
sudo chmod u+s,+x /usr/local/bin/docker-machine-driver-xhyve
$ sudo chmod u+s,+x /usr/local/bin/docker-machine-driver-xhyveCopy to Clipboard Copied! Toggle word wrap Toggle overflow
The downloaded docker-machine-driver-xhyve binary is compiled against a specific version of macOS. It is possible that the driver fails to work after a macOS version upgrade. In this case you can try to compile the driver from source:
For more information, see the xhyve driver documentation on GitHub.
1.3.2.3. Set up hypervisor on Windows リンクのコピーリンクがクリップボードにコピーされました!
Choose between Hyper-V (default on Windows 10) and VirtualBox (Windows 7 or Windows 10) for your hypervisor. Manual driver setup is required for Hyper-V. The driver is automatically configured if you install VirtualBox. However, a minishift command option (--vm-driver virtualbox) will be required later to identify VirtualBox to CDK.
On Windows with Hyper-V virtualization:
- Install Hyper-V.
- Add an External Virtual Switch. Verify that you pair the virtual switch with a network card (wired or wireless) that is connected to the network.
Set the environment variable
HYPERV_VIRTUAL_SWITCHto the name of the external virtual switch you want to use for CDK. For more information, see driver-specific environment variables.For example, on Command Prompt use:
set HYPERV_VIRTUAL_SWITCH=External (Wireless)
C:\> set HYPERV_VIRTUAL_SWITCH=External (Wireless)Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note that using quotes in Command Prompt results in the following error:
set HYPERV_VIRTUAL_SWITCH="External (Wireless)"
C:\> set HYPERV_VIRTUAL_SWITCH="External (Wireless)" Error creating the VM. Error with pre-create check: "vswitch \"\\\"External (Wireless)\\\"\" not found"Copy to Clipboard Copied! Toggle word wrap Toggle overflow However, on PowerShell you need to use the quotes:
PS C:\> $env:HYPERV_VIRTUAL_SWITCH="External (Wireless)"
PS C:\> $env:HYPERV_VIRTUAL_SWITCH="External (Wireless)"Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.3.3. Step 2: Download CDK Software リンクのコピーリンクがクリップボードにコピーされました!
Before you can download CDK software, you need to either register with the Red Hat Developer Program site or login to the Red Hat customer portal with Red Hat subscription credentials. Then go to one of the following two sites and download the software associated with your operating system:
Copy the downloaded minishift file to a directory in your PATH and make it executable. The downloaded executable is named cdk-3.2.0-1-minishift-darwin-amd64 (for macOS), cdk-3.2.0-1-minishift-linux-amd64 (for Linux) or cdk-3.2.0-1-minishift-windows-amd64.exe (for Windows). Assuming the executable is in the ~/Downloads directory, follow the procedure for your operating system:
For Red Hat Enterprise Linux:
mkdir -p ~/bin cp ~/Downloads/cdk-3.2.0-1-minishift* ~/bin/minishift chmod +x ~/bin/minishift export PATH=$PATH:$HOME/bin echo ‘export PATH=$PATH:$HOME/bin’ >> ~/.bashrc
$ mkdir -p ~/bin
$ cp ~/Downloads/cdk-3.2.0-1-minishift* ~/bin/minishift
$ chmod +x ~/bin/minishift
$ export PATH=$PATH:$HOME/bin
$ echo ‘export PATH=$PATH:$HOME/bin’ >> ~/.bashrc
For macOS:
mkdir -p ~/bin cp ~/Downloads/cdk-3.2.0-1-minishift* ~/bin/minishift chmod +x ~/bin/minishift export PATH=$PATH:$HOME/bin echo export PATH=$PATH:$HOME/bin >> ~/.bash_profile
$ mkdir -p ~/bin
$ cp ~/Downloads/cdk-3.2.0-1-minishift* ~/bin/minishift
$ chmod +x ~/bin/minishift
$ export PATH=$PATH:$HOME/bin
$ echo export PATH=$PATH:$HOME/bin >> ~/.bash_profile
For Windows:
Create the desired directory and copy the downloaded CDK binary to the directory, renaming the binary to minishift.exe. Add the directory path to the Windows PATH variable.
This directory must be on the C:\ drive!
If it’s difficult to get minishift.exe in your PATH, you can simply run it from the current directory as ./minishift.exe (or .\minishift.exe in some Windows shells).
1.3.4. Step 3: Set up CDK リンクのコピーリンクがクリップボードにコピーされました!
The minishift setup-cdk command gets and configures the components needed to run CDK on your system. By default, minishift setup-cdk places CDK content in your ~/.minishift directory (%USERPROFILE%/.minishift on Windows).
To use a directory other than ~/.minishift, you must set the --minishift-home flag and MINISHIFT_HOME environment variable, as described in Environment Variables.
Run the following command to set up CDK for Red Hat Enterprise Linux:
As you can see from the output, a .minishift directory is created in the user’s home directory to hold various CDK components, and appropriate files and settings are stored there.
For Windows or macOS: Running the same minishift setup-cdk command on Windows and macOS results in slightly different output, based on some different components and pathnames.
1.3.5. Optional: Use OpenShift Container Platform 3.7 リンクのコピーリンクがクリップボードにコピーされました!
Currently, CDK cannot automatically download the oc binary for OpenShift Container Platform 3.7. However, you may manually download the oc 3.7 binary to use it. To do so, follow these steps:
-
Ensure that you have run
minishift setup-cdk. -
Manually download the
ocbinary for OpenShift Container Platform 3.7 from https://mirror.openshift.com/pub/openshift-v3/clients/. -
Place the downloaded
ocbinary in the existing directory forocin MINISHIFT_HOME/cache/oc/v3.6.173.0.21/. Run CDK with the
--ocp-tagflag with the exact version of theoc3.7 binary. Example:minishift setup-cdk curl -O https://mirror.openshift.com/pub/openshift-v3/clients/3.7.9/linux/oc.tar.gz tar -zxvf oc.tar.gz cp oc ~/.minishift/cache/oc/v3.6.173.0.21 minishift start --ocp-tag v3.7.9
$ minishift setup-cdk $ curl -O https://mirror.openshift.com/pub/openshift-v3/clients/3.7.9/linux/oc.tar.gz $ tar -zxvf oc.tar.gz $ cp oc ~/.minishift/cache/oc/v3.6.173.0.21 $ minishift start --ocp-tag v3.7.9Copy to Clipboard Copied! Toggle word wrap Toggle overflow
When creating new profiles, CDK extracts the v3.6.173.0.21 oc binary from minishift rather than copying the oc binary placed in the cache. You must manually add the oc 3.7 binary to the cache for each profile to use OpenShift Container Platform 3.7. Use the following for each profile making use of the oc 3.7 binary:
-
Set the active profile via
minishift profile set <profile-name>. Follow the previous procedure using MINISHIFT_HOME/profiles/<profile-name>/cache/oc/v3.6.173.0.21/ as the cached
oclocation. Example:minishift profile set example minishift setup-cdk cp oc ~/.minishift/profiles/example/cache/oc/v3.6.173.0.21 minishift start --ocp-tag v3.7.9
$ minishift profile set example $ minishift setup-cdk $ cp oc ~/.minishift/profiles/example/cache/oc/v3.6.173.0.21 $ minishift start --ocp-tag v3.7.9Copy to Clipboard Copied! Toggle word wrap Toggle overflow
The --ocp-tag flag for minishift start expects version information in a specific format. Ensure that you prepend the oc version with "v" and replace any dashes with periods for use with the --ocp-tag flag. For example, if your oc version is 3.7.0-0.198.0, use the following:
minishift start --ocp-tag v3.7.0.0.198.0
$ minishift start --ocp-tag v3.7.0.0.198.0
1.3.6. Step 4: Start CDK リンクのコピーリンクがクリップボードにコピーされました!
The minishift start command launches CDK, which consists of a Red Hat Enterprise Linux virtual machine running OpenShift Container Platform. Follow these steps to launch CDK.
If you are using the default hypervisor for your operating system (KVM for Linux, xhyve for macOS, or Hyper-V for Windows), you can skip this step. If you have set up VirtualBox as your hypervisor, you need to configure the VirtualBox Driver. To switch the hypervisor used by CDK to VirtualBox, you have two choices:
-
Temporary: Add the
--vm-driver virtualboxoption to theminishift startcommand line to use VirtualBox immediately. -
Persistent: To persistently change the hypervisor, run the
minishift config set vm-driver virtualboxcommand. See the Persistent Configuration section for examples.
-
Temporary: Add the
By default,
minishift startprompts you for your Red Hat account username and password. You can enter that information or choose instead to:-
Skip registration: Add the
--skip-registrationoption tominishift startto not register the CDK VM. Register permanently: You can export registration information to environment variables so that
minishiftpicks it up automatically each time it starts as shown here:For Red Hat Enterprise Linux:
export MINISHIFT_USERNAME=<RED_HAT_USERNAME> export MINISHIFT_PASSWORD='<RED_HAT_PASSWORD>' echo export MINISHIFT_USERNAME=$MINISHIFT_USERNAME >> ~/.bashrc echo export MINISHIFT_PASSWORD=$MINISHIFT_PASSWORD >> ~/.bashrc
$ export MINISHIFT_USERNAME=<RED_HAT_USERNAME> $ export MINISHIFT_PASSWORD='<RED_HAT_PASSWORD>' $ echo export MINISHIFT_USERNAME=$MINISHIFT_USERNAME >> ~/.bashrc $ echo export MINISHIFT_PASSWORD=$MINISHIFT_PASSWORD >> ~/.bashrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow For macOS:
export MINISHIFT_USERNAME='<RED_HAT_USERNAME>' export MINISHIFT_PASSWORD='<RED_HAT_PASSWORD>' echo export MINISHIFT_USERNAME=$MINISHIFT_USERNAME >> ~/.bash_profile echo export MINISHIFT_PASSWORD=$MINISHIFT_PASSWORD >> ~/.bash_profile
export MINISHIFT_USERNAME='<RED_HAT_USERNAME>' export MINISHIFT_PASSWORD='<RED_HAT_PASSWORD>' echo export MINISHIFT_USERNAME=$MINISHIFT_USERNAME >> ~/.bash_profile echo export MINISHIFT_PASSWORD=$MINISHIFT_PASSWORD >> ~/.bash_profileCopy to Clipboard Copied! Toggle word wrap Toggle overflow For Windows:
Using Command Prompt:
setx MINISHIFT_USERNAME <RED_HAT_USERNAME> setx MINISHIFT_PASSWORD <RED_HAT_PASSWORD>
C:\> setx MINISHIFT_USERNAME <RED_HAT_USERNAME> C:\> setx MINISHIFT_PASSWORD <RED_HAT_PASSWORD>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Using PowerShell:
PS> $env:MINISHIFT_USERNAME = '<RED_HAT_USERNAME>' PS> $env:MINISHIFT_PASSWORD = '<RED_HAT_PASSWORD>'
PS> $env:MINISHIFT_USERNAME = '<RED_HAT_USERNAME>' PS> $env:MINISHIFT_PASSWORD = '<RED_HAT_PASSWORD>'Copy to Clipboard Copied! Toggle word wrap Toggle overflow
-
Skip registration: Add the
Run
minishift startto set up and start the virtual machine with the default configuration. See theminishift startcommand reference to see other options for modifyingminishift start. Here is an example of how that would look run from a Red Hat Enterprise Linux system:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run this command to see if the virtual machine is running:
minishift status
$ minishift status RunningCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You will see similar output from minishift start when run in a macOS terminal or Windows command prompt or PowerShell.
1.3.7. Step 5: Configure CDK リンクのコピーリンクがクリップボードにコピーされました!
With the CDK virtual machine running, you can configure and start using CDK through two primary interfaces: oc (OpenShift client binary command) or the OpenShift web console.
oc: Useminishift oc-envto display the command you need to type into your shell in order to add theocbinary to yourPATHenvironment variable. The output ofminishift oc-envwill differ depending on your user directory, operating system and shell type.For Red Hat Enterprise Linux:
minishift oc-env Run this command to configure your shell: eval $(minishift oc-env)
$ minishift oc-env export PATH="/home/joe/.minishift/cache/oc/v3.6.173.0.21:$PATH" # Run this command to configure your shell: # eval $(minishift oc-env)Copy to Clipboard Copied! Toggle word wrap Toggle overflow Use the following to add the
occommand to yourPATHvia the ~/.bashrc file:echo export PATH=\"/home/joe/.minishift/cache/oc/v3.6.173.0.21:\$PATH\" >> ~/.bashrc source ~/.bashrc
$ echo export PATH=\"/home/joe/.minishift/cache/oc/v3.6.173.0.21:\$PATH\" >> ~/.bashrc $ source ~/.bashrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow For macOS:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For Windows:
Add the path to the
ocbinary to yourPATHenvironment variable.
For more information about interacting with OpenShift from the command-line interface, see the OpenShift Client Binary section.
OpenShift web console: To access OpenShift from the web console, you can either:
-
Run
minishift consoleto open the OpenShift web console from your default browser or -
Open a browser to the URL output from the
minishift startcommand (for example, https://192.168.42.60:8443).
From the web console screen, enter the user name (developer) and password (developer) displayed from the output.
-
Run
You are now ready to start using OpenShift using either of those two interfaces.
1.3.8. Deploying a Sample Application リンクのコピーリンクがクリップボードにコピーされました!
OpenShift provides various sample applications, such as templates, builder applications, and quickstarts. To begin creating an application, see:
-
Creating an Application Using the CLI to use the
occommand to create a new application. - Creating an Application Using the Web Console to use the OpenShift web user interface to create applications.
The following steps describe how to deploy a sample Node.js application from the command-line.
Create a Node.js example app:
oc new-app https://github.com/openshift/nodejs-ex -l name=myapp
$ oc new-app https://github.com/openshift/nodejs-ex -l name=myappCopy to Clipboard Copied! Toggle word wrap Toggle overflow Track the build log until the app is built and deployed:
oc logs -f bc/nodejs-ex
$ oc logs -f bc/nodejs-exCopy to Clipboard Copied! Toggle word wrap Toggle overflow Expose a route to the service:
oc expose svc/nodejs-ex
$ oc expose svc/nodejs-exCopy to Clipboard Copied! Toggle word wrap Toggle overflow Access the application:
minishift openshift service nodejs-ex --in-browser
$ minishift openshift service nodejs-ex --in-browserCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you are done with the VM, use
minishift stopto stop the VM temporarily. You can return to the same state later withminishift start.minishift stop
$ minishift stop Stopping local OpenShift cluster... Stopping "minishift"...Copy to Clipboard Copied! Toggle word wrap Toggle overflow
See minishift stop for details on managing subscriptions as you stop and start the VM.
For more information about creating applications in OpenShift, see Creating New Applications in the OpenShift documentation.
1.4. Uninstalling CDK リンクのコピーリンクがクリップボードにコピーされました!
1.4.1. Overview リンクのコピーリンクがクリップボードにコピーされました!
This section describes how you can uninstall the minishift binary and delete associated files.
1.4.2. Uninstalling CDK リンクのコピーリンクがクリップボードにコピーされました!
Delete the CDK VM and any VM-specific files:
minishift delete
$ minishift deleteCopy to Clipboard Copied! Toggle word wrap Toggle overflow This command deletes everything in the MINISHIFT_HOME/.minishift/machines/minishift directory. Other cached data and the persistent configuration are not removed.
To completely uninstall CDK, delete everything in the MINISHIFT_HOME directory (default ~/.minishift) and ~/.kube:
For Red Hat Enterprise Linux and macOS:
rm -rf ~/.minishift rm -rf ~/.kube
$ rm -rf ~/.minishift $ rm -rf ~/.kubeCopy to Clipboard Copied! Toggle word wrap Toggle overflow For Windows PowerShell:
Replace
<MINISHIFT_HOME>with the location of your home directory.PS C:\> Remove-Item -Recurse -Force C:\<MINISHIFT_HOME>\.minishift\ PS C:\> Remove-Item -Recurse -Force C:\<MINISHIFT_HOME>\.kube\
PS C:\> Remove-Item -Recurse -Force C:\<MINISHIFT_HOME>\.minishift\ PS C:\> Remove-Item -Recurse -Force C:\<MINISHIFT_HOME>\.kube\Copy to Clipboard Copied! Toggle word wrap Toggle overflow For Windows command prompt:
Replace
<MINISHIFT_HOME>with the location of your home directory. (You may need to use thedel /scommand instead.)rm -r c:\<MINISHIFT_HOME>\.minishift rm -r c:\<MINISHIFT_HOME>\.kube
c:\> rm -r c:\<MINISHIFT_HOME>\.minishift c:\> rm -r c:\<MINISHIFT_HOME>\.kubeCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
With your hypervisor management tool, confirm that there are no remaining artifacts related to the CDK VM. For example, if you use KVM, you need to run the
virshcommand.