The images, containers, volumes and networks that I had in my system have disappeared.

### Description

The images, containers, volumes and networks that I had in my system have disappeared. This is the second time it has happened.

My system is a MacBook Pro Ventura
13.4.1 (c) (22F770820d)

I would like to know what is the root cause of this?

On some occasions I was able to recover them by installing Docker Desktop and the route appeared
/Library/Containers/com.docker.docker/Data/vms/0/images

From there I was able to extract and save all my information, but today, as I don't use Docker Desktop, it doesn't appear.

**Could you provide me with information on which system folder these images are hosted on, please?**

There may be an application bug.

I use this configuration:

HomeDesktop sujeto$ colima list
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running x86_64 4 8GiB 60GiB docker

HomeDesktop sujeto$ docker context list
NAME DESCRIPTION DOCKER ENDPOINT ERROR
colima * colima unix:///Users/user/.colima/default/docker.sock
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock

Thanks a lot.

### Version

HomeDesktop:Data sujeto$ colima version && limactl --version && qemu-img --version
colima version 0.6.1
git commit: fa1bc249f921287745f01fb02075c9ecbb491c31

runtime: docker
arch: x86_64
client: v24.0.7
server: v24.0.5
limactl version 0.18.0
qemu-img version 8.1.2
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [ ] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

HomeDesktop: Data sujeto$ colima status
INFO[0009] colima is running using QEMU
INFO[0009] arch: x86_64
INFO[0009] runtime: docker
INFO[0009] mountType: 9p
INFO[0009] socket: unix:///Users/sujeto/.colima/default/docker.sock

### Reproduction Steps

1. colima start
2. colima status
3. docker images
4. docker ps -a

### Expected behaviour

Watch all the containers created previously.

### Additional context

_No response_