abiosoft / abiosoft/colima

Intermittent freezing of vm on M1+Ventura while using DDEV fixed with Link-Local Only IPv6 setting on Mac

Abierto
#686 10 comentarios 2 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Go
Estrellas
30.8k
Forks
613
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Description

After upgrading to Ventura 13.2.1 and 13.3, my colima vm would intermittently freeze - not responding to any ddev commands, nor `colima status`. After issuing any ddev or colima command and waiting several minutes, I would do a `ctrl-c` to get the terminal back.

Searching through the issue queue, I found this [post](https://github.com/abiosoft/colima/issues/683) and in particular [this comment](https://github.com/abiosoft/colima/issues/683#issuecomment-1493658406) where it's mentioned:

> Under Mac, I went to my network, selected the interface, goto TCP/IP settings and set "Configure IPv6" to "Link-Local Only" - reboot and it is now working!

I did the same with my Macbook - I changed the settings via the Mac's network gui so that IPv6 was set to `Link-Local Only` and the intermittent freezing seems to have disappeared.

### Version

Colima Version: HEAD-65ee3d2
Lima Version: 0.15.0
Qemu Version: 7.2.0 (although I'm using `--vm-type vz`)

### Operating System

- [ ] macOS Intel <= 12 (Monterrey)
- [ ] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [X] macOS M1 >= 13 (Ventura)
- [ ] Linux

### Output of `colima status`

INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users//.colima/default/docker.sock

### Reproduction Steps

1. `colima start --cpu 4 --memory 8 --vm-type vz`
2. Start a ddev project with `ddev start`
3. Visit local ddev site started in previous step and do normal development tasks via the browser and using `ddev drush *`
4. In the space of three minutes to an hour, eventually the site stops responding, and entering ddev and colima commands stick indefinitely and eventually need killing with a ctrl-c.
5. Only a `killall limactl` seems to allow resumption, although it means doing a `colima start` and beginning again.

### Expected behaviour

I would expect that the environment created by colima to continue to function reliably for an indefinite period.

### Additional context

As I don't have a specific need for IPv6 at the moment, and my Mac seems to be fine with IPv6 being configured as `Link-Local Only`, I'm happy with that as a solution and possibly for it to be a long term solution. Perhaps there is absolutely nothing wrong with Colima, and there is something weird going on with MacOS.

This might be a helpful solution to others.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.