Andreas Allacher

Results 149 comments of Andreas Allacher

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft yes, qemu version seems to work fine and also I had another colleague try it on an M2 (delete / start) and there it worked fine. but I got...

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft I also just tried the following lima config and manually creating it, and it fails as well with expanding disk: ```yaml images: - location: 'https://github.com/abiosoft/colima-core/releases/download/v0.6.7/ubuntu-23.10-minimal-cloudimg-amd64.qcow2' arch: 'x86_64' digest: 'sha512:9980ac00edc0a0b75e9c924f25f3403e76ef8fd680ee1847082de543a8ff851413992a18b065c53092edf298d11de50b0b129ece1ec17217bd8a6e9266b22345'...

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft I did one more test and the following did indeed work (using limactl manually): download and convert image manually to raw using qemu-img ```sh curl -o ubuntu-23.10-minimal-cloudimg-amd64.qcow2 -L https://github.com/abiosoft/colima-core/releases/download/v0.6.7/ubuntu-23.10-minimal-cloudimg-amd64.qcow2...

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft The easiest solution would be to switch back to the raw image type until the lima bug is fixed. at least for intel macs when using vmtype vz. not...

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft that would be even better. strictly speaking it could always be done for now for VZ vm type, as lima does the conversion anyway. Any idea when the corresponding...

0.6.7 - Initialization of base image fails / stuck at "expanding disk" - macOS Intel with vmtype vz and virtioifs

@abiosoft any news when this might be fixed? as it bascially prevents me to do a colima delete (though it is probably not necessary now that I have it running...

vz A lima _disk converted from qcow2 > raw on startup truncates to 0 bytes and can't be used in the vm.

I am not 100% sure it is related to this issue, but it seems related. I just had an issue with the new colima version that changed from raw format...

vz A lima _disk converted from qcow2 > raw on startup truncates to 0 bytes and can't be used in the vm.

Btw. from my checks with colima 0.6.7 I did some checks on the file on the disk and it seems that the temporary filename is not changed after the disk...

vz A lima _disk converted from qcow2 > raw on startup truncates to 0 bytes and can't be used in the vm.

what is the state regarding this issue? does anyone know if OS or latest lima update might have fixed this? don't have time currently to test this.

Move package.json files for tests to a different folders (admin and storefront), e.g. a subfolder tests

@boxblinkracer Dev dependencies can be required by webpack to correctly do the dependency build. E.g. usually in dependencies one puts things that are deployed in the end but things like...