Crc: [BUG] Windows: CRC binary must be on same drive where user's home directory is located
General information
- OS: Windows
- Hypervisor: Hyper-V
- Did you run
crc setupbefore starting it (Yes/No)? Yes
CRC version
version: 1.0.0-beta.3-4.1.11+e97bf65
Steps to reproduce
- Have CRC binary on different drive than $HOME
- Run
crc start
Expected
CRC starts
Actual
ERRO Error occurred: Error creating host: Error creating the VM. Error creating machine: Error in driver during machine creation: open /Users/jonst/.crc/cache/crc_hyperv_4.1.11/crc.vhdx: The system cannot find the path specified.
Moving the CRC binary to the same drive where that path exists things progress further.
jds2001
All 11 comments
crc binary doesn't like being on a different drive than the user's homedir 😃
We will see what can be done about this. But yes, this is a 'known issue' that we kind of forgot about, as it occured during the time of Minishift. Perhaps this can be resolved, else we might add documentation (which is always a good idea to do first).
gbraad
on 8 Sep 2019
Same Error comes if the machine does not have enough memory.
rchhatwal
on 12 Nov 2019
Default VM for crc needs 8GB.
rchhatwal
on 12 Nov 2019
Same Error comes if the machine does not have enough memory.
This is a different issue.
gbraad
on 12 Nov 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 11 Feb 2020
This is still an issue.
nottheswimmer
on 1 May 2020
764 windrive
gbraad
on 7 May 2020
This is still an issue. I keep my code on a separate drive for various reasons from my boot drive. This is Windows 10 pro Build 18363
On the non-home directory drive it is this....
PS C:\Users\
PS G:> cd .\code\crc4win\crc-windows-1.11.0-amd64\
PS G:\code\crc4win\crc-windows-1.11.0-amd64> ./crc start -p ..\pull-secret4Deathstar.txt
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
INFO Checking if Hyper-V service is enabled
INFO Checking if the Hyper-V virtual switch exist
INFO Found Virtual Switch to use: Default Switch
INFO Loading bundle: crc_hyperv_4.4.5.crcbundle ...
INFO Checking size of the disk image C:\Users\
INFO Creating CodeReady Containers VM for OpenShift 4.4.5...
ERRO Error creating host: Error creating the VM: Error creating machine: Error in driver during machine creation: open /Users/
Note that this is my G drive...
Now moved to C drive
PS C:\Users\
PS C:\Users\
PS C:\Users\
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
INFO Checking if Hyper-V service is enabled
INFO Checking if the Hyper-V virtual switch exist
INFO Found Virtual Switch to use: Default Switch
INFO Loading bundle: crc_hyperv_4.4.5.crcbundle ...
INFO Checking size of the disk image C:\Users\
INFO Creating CodeReady Containers VM for OpenShift 4.4.5...
INFO CodeReady Containers VM is running
INFO Verifying validity of the cluster certificates ...
INFO Will run as admin: add dns server address to interface vEthernet (Default Switch)
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Generating new SSH key
INFO Copying kubeconfig file to instance dir ...
INFO Starting OpenShift kubelet service
INFO Configuring cluster for first start
INFO Adding user's pull secret ...
INFO Updating cluster ID ...
INFO Starting OpenShift cluster ... [waiting 3m]
INFO
INFO To access the cluster, first set up your environment by following 'crc oc-env' instructions
INFO Then you can access it by running 'oc login -u developer -p developer https://api.crc.testing:6443'
INFO To login as an admin, run 'oc login -u kubeadmin -p 8rynV-SeYLc-h8Ij7-YPYcz https://api.crc.testing:6443'
INFO
INFO You can now run 'crc console' and use these credentials to access the OpenShift web console
Started the OpenShift cluster
WARN The cluster might report a degraded or error state. This is expected since several operators have been disabled to lower the resource usage. For more information, please consult the documentation
michaelrishiforrester
on 10 Jun 2020
This is a known issue and recorded as such in the release notes.
On Wed, Jun 10, 2020 at 11:17 PM Michael R Forrester <
[email protected]> wrote:
This is still an issue. I keep my code on a separate drive for various
reasons from my boot drive. This is Windows 10 pro Build 18363
On the non-home directory drive it is this....
PS C:\Users> g:
PS G:> cd .\code\crc4win\crc-windows-1.11.0-amd64
PS G:\code\crc4win\crc-windows-1.11.0-amd64> ./crc start -p
..\pull-secret4Deathstar.txt
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
INFO Checking if Hyper-V service is enabled
INFO Checking if the Hyper-V virtual switch exist
INFO Found Virtual Switch to use: Default Switch
INFO Loading bundle: crc_hyperv_4.4.5.crcbundle ...
INFO Checking size of the disk image
C:\Users.crc\cache\crc_hyperv_4.4.5\crc.vhdx ...
INFO Creating CodeReady Containers VM for OpenShift 4.4.5...
ERRO Error creating host: Error creating the VM: Error creating machine:
Error in driver during machine creation: open
/Users//.crc/cache/crc_hyperv_4.4.5/crc.vhdx: The system
cannot find the path specified.
Note that this is my G drive...
Now moved to C drive
PS C:\Users> cd .\crc4win
PS C:\Users\crc4win> cd .\crc-windows-1.11.0-amd64
PS C:\Users\crc4win\crc-windows-1.11.0-amd64> ./crc
start -p ..\pull-secret4Deathstar.txt
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking if running as normal user
INFO Checking Windows 10 release
INFO Checking if Hyper-V is installed and operational
INFO Checking if user is a member of the Hyper-V Administrators group
INFO Checking if Hyper-V service is enabled
INFO Checking if the Hyper-V virtual switch exist
INFO Found Virtual Switch to use: Default Switch
INFO Loading bundle: crc_hyperv_4.4.5.crcbundle ...
INFO Checking size of the disk image
C:\Users.crc\cache\crc_hyperv_4.4.5\crc.vhdx ...
INFO Creating CodeReady Containers VM for OpenShift 4.4.5...
INFO CodeReady Containers VM is running
INFO Verifying validity of the cluster certificates ...
INFO Will run as admin: add dns server address to interface vEthernet
(Default Switch)
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Generating new SSH key
INFO Copying kubeconfig file to instance dir ...
INFO Starting OpenShift kubelet service
INFO Configuring cluster for first start
INFO Adding user's pull secret ...
INFO Updating cluster ID ...
INFO Starting OpenShift cluster ... [waiting 3m]
INFO
INFO To access the cluster, first set up your environment by following
'crc oc-env' instructions
INFO Then you can access it by running 'oc login -u developer -p developer
https://api.crc.testing:6443'
INFO To login as an admin, run 'oc login -u kubeadmin -p
8rynV-SeYLc-h8Ij7-YPYcz https://api.crc.testing:6443'
INFO
INFO You can now run 'crc console' and use these credentials to access the
OpenShift web console
Started the OpenShift cluster
WARN The cluster might report a degraded or error state. This is expected
since several operators have been disabled to lower the resource usage. For
more information, please consult the documentation—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/559#issuecomment-642077746, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZUSFR6GA7E54DSAEADRV6PY3ANCNFSM4IUSDXFQ
.
--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]
gbraad
on 10 Jun 2020
Default VM for crc needs 8GB.
i am also facing this same problem, inspite of moving to c drive same issue. how can i fix the memory issue in windows 10 pro. i have 16 gb ram
sannamalai76
on 6 Jul 2020
Removing the "kind/documentation" label, as this is already documented as a known issue.
robin-owen
on 11 Aug 2020
Related issues
mojotx
·
3Comments
skabashnyuk
·
3Comments
aceeric
·
4Comments
ktdreyer
·
8Comments
omkensey
·
8Comments