Chapter 6. Issues on Microsoft Windows
This section describes Red Hat OpenShift Local issues that affect users on a Microsoft Windows host.
6.1. Completing the installation after installation with the Microsoft Standard Installer (MSI)
Procedure
- Install Red Hat OpenShift Local with the MSI installer
- Reboot your computer
Run the command in Command Prompt or PowerShell:
$ crc setup
6.2. The crc cleanup command might fail with a permission error
Running crc setup followed by crc cleanup without restarting your host computer between commands will cause crc cleanup to report the following error:
Post "http://unix/clean": open \\.\pipe\crc-admin-helper: Access is denied.
Workaround
- Reboot your computer
Run the command:
$ crc cleanup
6.3. Unexpected behavior when run outside %WINDRIVE%
The Hyper-V driver will fail when you start the crc binary from a network drive.
Workaround
Move the
crcbinary to a location on%WINDRIVE%.%WINDRIVE%is usually set toC:\.
6.4. Red Hat OpenShift Local expects FullLanguage support in PowerShell
Red Hat OpenShift Local supports the ConstrainedLanguage PowerShell mode with exceptions determined by your system administrator.
6.5. The crc oc-env command does not work with special characters in %PATH%
On Microsoft Windows, PowerShell and Command Prompt do not use the UTF-8 encoding. Therefore, running the crc oc-env command with special characters present in the %PATH% will not accurately encode UTF-8 characters.
Workaround
-
Move the
crcbinary to a location containing no special characters.
Additional resources
- See the Red Hat OpenShift Local Getting Started Guide for an overview of Red Hat OpenShift Local features and an introduction to OpenShift Container Platform.
-
Report issues with Red Hat OpenShift Local or request features by using the OpenShift Container Platform product with the
crccomponent on Red Hat Bugzilla.