Colima fails to start Rosetta, and reports that it's not installed.
- Langage dominant
- Go
- Étoiles
- 30.8k
- Forks
- 613
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Description
Colima detects if Rosetta is running and if it's not Colima will ask the user to install Rosetta 2.
The [RosettaRunning](https://github.com/abiosoft/colima/blob/8d349191294f98d63b6ef5e2463c67125e84fd1d/util/macos.go#L81) function does the correct thing (checks if it's running), but for some reason the same function is called in [colima/environment/vm/lima/yaml.go](https://github.com/abiosoft/colima/blob/main/environment/vm/lima/yaml.go#L36) to determine if it's installed.
In my case I have Rosetta installed, and when I call `colima start` I get a warning message noting that rosetta isn't installed, and asking me to install Rosetta. Colima then falls back to a very slow QEMU instance (comparison [here](https://github.com/ctrlok/macdockergeek/issues/3)).
I installed it so many times believing that it was being removed somehow. Thankfully, I'm able to look at the code (others might not get that far) to see what the issue is.
The ideal solution:
* Detect if Rosetta is **installed**
* If Rosetta is installed (and required), start it.
### Version
```
colima version 0.6.9
git commit: c3a31ed05f5fab8b2cdbae835198e8fb1717fd0f
runtime: docker
arch: aarch64
client: v27.0.3
server: v26.1.1
limactl version 0.22.0
qemu-img version 9.0.2
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
```
### Operating System
- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [x] Apple Silicon >= 14 (Sonoma)
- [ ] 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/jd/.colima/default/docker.sock
```
### Reproduction Steps
`$ colima start`
### Expected behaviour
Colima uses Rosetta if installed and configured.
### Additional context
_No response_
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.