Location of VM Disk Changed
- Vorherrschende Sprache
- Go
- Sterne
- 30.8k
- Forks
- 613
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Description
It seems that newer versions of colima (v0.6+) changed the default folder where it stores its VM disk data from `~/.lima` to `~/.colima`.
This triggers our laptop backup software to backup the ever changing VM disk which can cause the backup process to never complete and also upload zeroed data to the backup servers.
How can we configured this location to put it back to the way it was? The reason I ask this is that we do not have control over the exempt backup locations and it took a really long time to get our IT team to get `~/.lima` exempt. I would rather not go through that process again for `~/.colima`.
### Version
v0.6.2
### Operating System
- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux
### Output of `colima status`
_No response_
### Reproduction Steps
_No response_
### Expected behaviour
Lima VMs stay in `~/.lima/colima`.
### Additional context
_No response_
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.