Chapter 6. Issues on Microsoft Windows
This section describes Red Hat OpenShift Local issues that affect users on a Microsoft Windows host.
crc setup command must be run following installation with the MSI installer
After installing Red Hat OpenShift Local with the MSI installer and rebooting your computer, ensure you run the
crc setup command in Command Prompt or PowerShell to complete the installation.
crc cleanup command may fail with a permission error
crc setup followed by
crc cleanup without restarting your host machine between commands will cause
crc cleanup to report the following error:
Post "http://unix/clean": open \\.\pipe\crc-admin-helper: Access is denied.
To complete the
crc cleanup command, restart your host machine and run the command again.
6.3. Unexpected behavior when run outside of
The Hyper-V driver will fail when the
crc binary is executed from a network drive. The
crc binary must be placed in a location on
%WINDRIVE% is normally set to
6.4. Red Hat OpenShift Local expects
FullLanguage support in PowerShell
ConstrainedLanguage PowerShell mode is supported with exceptions determined by your system administrator.
crc oc-env command does not work with special characters in
On Microsoft Windows, PowerShell and Command Prompt do not use the UTF-8 encoding. As a result, running the
crc oc-env command with special characters present in the
%PATH% will not accurately encode UTF-8 characters. There is no known workaround for this issue.
- See the Red Hat OpenShift Local Getting Started Guide for an overview of Red Hat OpenShift Local features and an introduction to the use of OpenShift Container Platform.
Report issues with Red Hat OpenShift Local or request new features using the OpenShift Container Platform product with the
crccomponent on Red Hat BugZilla.