How do I get access to build cache images?

When building Docker images in Linux, Docker lists the intermediate containers as it is building. Using that information, I can troubleshoot build errors by doing a `docker run -it --entrypoint bash ` and then manually running the failing step in the container and diagnosing the problem. Is there a way to get this information from Colima?

See below for standard Docker build output:
```
Running hooks in /etc/ca-certificates/update.d...
done.
Removing intermediate container e310f773f285
---> 46fe879e475e
Step 3/89 : RUN ln -s /usr/bin/python3 /usr/bin/python
---> Running in 746c5a0174b9
Removing intermediate container 746c5a0174b9
---> 6026575ae4ed
Step 4/89 : ENV ASPNETCORE_URLS=http://+:80 DOTNET_RUNNING_IN_CONTAINER=true
---> Running in 664f383847a6
Removing intermediate container 664f383847a6
---> 75e6d249122a
Step 5/89 : RUN dotnet_version=3.1.9 && curl -SL --output dotnet.tar.gz https://dotnetcli.azureedge.net/dotnet/Runtime/$dotnet_version/dotnet-runtime-$dotnet_version-linux-x64.tar.gz && mkdir -p /usr/share/dotnet && tar -ozxf dotnet.tar.gz -C /usr/share/dotnet && rm dotnet.tar.gz && ln -s /usr/share/dotnet/dotnet /usr/bin/dotnet
---> Running in e8e75348c4bb

```

As you can see, the layer image ID for each step is listed.

Thanks for the great project!

The issue asks for a way to access intermediate container images during a Docker build in Colima, similar to standard Docker output. Look at Colima's build command implementation to see how it interfaces with the container runtime (containerd). Check if build cache or intermediate layer information is exposed. The first step is to understand the current build output format and where layer IDs are logged. 'Done' means the feature is implemented and the user can retrieve intermediate image IDs for debugging.

Escrito por el modelo de indexación a partir del texto del issue.