crc: [BUG] crc 1.18 crc config set disk-size not respected on macos
Trying to set the disk size to 50GB with crc config set disk-size 50 doesn’t work
General information
- OS: macOS
- Hypervisor: hyperkit
- Did you run
crc setupbefore starting it (Yes/No)? Yes - Running CRC on: Laptop
CRC version
❯ crc version
CodeReady Containers version: 1.18.0+bb304aa
OpenShift version: 4.6.1 (embedded in binary)
CRC status
crc status --log-level debug
DEBU CodeReady Containers version: 1.18.0+bb304aa
DEBU OpenShift version: 4.6.1 (embedded in binary)
Checking file: /Users/csantana23/.crc/machines/crc/.crc-exist
DEBU About to run SSH command with hidden output
DEBU SSH command succeeded
DEBU image-registry operator is degraded, Reason: ImagePrunerJobFailed
DEBU About to run SSH command:
df -B1 --output=size,used,target /sysroot | tail -1
DEBU SSH command results: err: <nil>, output: 32720793600 12768727040 /sysroot
CRC VM: Running
OpenShift: Running (v4.6.1)
Disk Usage: 12.77GB of 32.72GB (Inside the CRC VM)
Cache Usage: 15.26GB
Cache Directory: /Users/csantana23/.crc/cache
CRC config
crc config view
- cpus : 6
- disk-size : 50
- memory : 20384
Host Operating System
sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H2
Steps to reproduce
- crc delete
- crc setup
- crc config set cpus 6
- crc config set memory 20384
- crc config set disk-size 50
Expected
Expect VM disk size to be 50GB
Actual
VM Disk size is the default 33GB
Logs
crc start -p ~/Downloads/pull-secret.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 minimum RAM requirements
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
INFO Checking if crc-driver-hyperkit is installed
INFO Checking file permissions for /etc/hosts
INFO Checking file permissions for /etc/resolver/testing
INFO Loading bundle: crc_hyperkit_4.6.1.crcbundle ...
INFO Checking size of the disk image /Users/csantana23/.crc/cache/crc_hyperkit_4.6.1/crc.qcow2 ...
INFO Creating CodeReady Containers VM for OpenShift 4.6.1...
INFO CodeReady Containers VM is running
INFO Generating new SSH Key pair ...
INFO Updating authorized keys ...
INFO Copying kubeconfig file to instance dir ...
INFO Starting network time synchronization in CodeReady Containers VM
INFO Network restart not needed
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Adding user's pull secret to instance disk...
INFO Verifying validity of the kubelet certificates ...
INFO Starting OpenShift kubelet service
INFO Configuring cluster for first start
INFO Adding user's pull secret to the cluster ...
INFO Updating cluster ID ...
INFO Starting OpenShift cluster ... [waiting 3m]
INFO Updating kubeconfig
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
Started the OpenShift cluster
Tried to pass via flag -d and I get WARN messages, I get same result VM is 33GB
crc start -p ~/Downloads/pull-secret.txt -d 50
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking minimum RAM requirements
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
INFO Checking if crc-driver-hyperkit is installed
INFO Checking file permissions for /etc/hosts
INFO Checking file permissions for /etc/resolver/testing
INFO Starting CodeReady Containers VM for OpenShift 4.6.1...
WARN Memory configuration change has been ignored as the machine driver does not support it
WARN CPU configuration change has been ignored as the machine driver does not support it
WARN Disk size configuration change has been ignored as the machine driver does not support it
INFO CodeReady Containers VM is running
INFO Starting network time synchronization in CodeReady Containers VM
INFO Network restart not needed
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Verifying validity of the kubelet certificates ...
INFO Starting OpenShift kubelet service
INFO Starting OpenShift cluster ... [waiting 3m]
INFO Updating kubeconfig
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (10 by maintainers)
@csantanapr if you really need it now, you can take qcow-tool here https://github.com/code-ready/machine-driver-hyperkit/releases/tag/v0.12.9 and use it to resize your disk. Then inside, the VM you still need to run xfs_growfs.
It is not yet implemented on macOS.