Vz/VirtioFS 0.5.2 SEGFAULT, SEGV failures in colima and in DDEV

[rfay]

Description

Running Colima 0.5.1/0.5.2 with vz/VirtioFS I've seen a number of SEGFAULTS in these situations:

• Running ddev start:

+ cp -r /mnt/ddev_config/nginx_full /etc/nginx/sites-enabled/
/start.sh: line 43:    13 Segmentation fault      cp -r /mnt/ddev_config/nginx_full /etc/nginx/sites-enabled/

• Attempting to colima ssh and sudo -s

Version

Colima Version: 0.5.2
Lima Version: 0.14.2
Qemu Version:

Operating System

• macOS Intel <= 12 (Monterrey)
• macOS Intel >= 13 (Ventura)
• macOS M1 <= 12 (Monterrey)
• macOS M1 >= 13 (Ventura)
• Linux

Output of colima status

$ colima status -p vz-virt
INFO[0000] colima [profile=vz-virt] is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/rfay/.colima/vz-virt/docker.sock

Reproduction Steps

I don't think I've been able to get consistent results

Expected behaviour

No SEGV

Additional context

No response

[balajiv113]

Just for confirmation,
Does VM itself crashes after these segfault ??

[rfay]

In the second case (colima ssh and then sudo -s) the VM apparently crashes.

In the first case (in a regular container start) it's repeatable without restarting anything, so I assume the VM hasn't crashed.

[rfay]

I imagine this is obsolete, closing.