Colima doesn't respect large disk size argument

[Kshyshtoph]

Hello, I've ran into issue running multiple services locally with Colima. I need quite a bunch of disk space, so I start it with
colima start --cpu 16 --memory 48 --disk 560 --vm-type=vz-rosetta. Although the output of colima list seems in tact:

PROFILE    STATUS     ARCH       CPUS    MEMORY    DISK      RUNTIME    ADDRESS
default    Running    aarch64    16      48GiB     560GiB    docker     192.168.64.2

The actual disk space I have avaliable seemed weirdly low (I kept getting "no space left on the device"). After a little investigation I ran colima ssh -- df -h /usr/local and it seems the machine only has 116G of disk space (instead of desired 560):

colima ssh -- df -h /usr/local
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       116G  116G     0 100% /

Is there any way to actually go beyond 116G?

[lmgarret]

Running into a similar issue: I've provisioned for a 150Gi disk, restarted colima, and saw the disk resizing step succeed.
But when I colima list:

PROFILE    STATUS     ARCH       CPUS    MEMORY    DISK      RUNTIME    ADDRESS
default    Running    aarch64    6       12GiB     150GiB    docker

and I check the disk size with colima ssh -- df -h /usr/local, I get two completely different values:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        19G  2.3G   17G  13% /

[abiosoft]

Colima actually uses a separate disk for the container runtime.

This should reveal the disk size.

colima ssh -- df -h /var/lib/docker

[abiosoft]

@Kshyshtoph are you interacting with the VM directly or you are using docker.

[Kshyshtoph]

I am using docker, but actually I've managed to find the cause of my issue. It's kinda embarrassing, but let me share so future generations can learn from it.

Turned out I was a little short on disk size available to the colima vm - when I actually checked available space with df -h ~/.colima I got Avail 521Gi - there was no complaint about available space during colima start, but when I ran with --disk 460 the VM was properly created and colima ssh -- df -h /usr/local got me an expected available space