Regression on first-time use of ~/.docker/certs.d: Library/Caches/colima/docker-certs: No such file or directory

[AlexanderOMara]

Description

With the latest update, when ~/.docker/certs.d is created for the first time, it appears to fail to copy certs inside colima, and the following warning is seen on start.

$ colima start
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0000] starting ...                                  context=vm
WARN[0021] cannot copy registry certs to vm: error running [rm -r /Users/user/Library/Caches/colima/docker-certs], output: "rm: /Users/user/Library/Caches/colima/docker-certs: No such file or directory", err: "exit status 1"  context=vm
INFO[0021] provisioning ...                              context=docker
INFO[0022] starting ...                                  context=docker
INFO[0023] done

It's possible to make the directory manually and after restarting colima things start working correctly and continuously until/unless the cache directory is removed, but I think this could be handled more-gracefully.

Version

$ colima version && limactl --version && qemu-img --version
colima version 0.7.5
git commit: 1588c066b9ab9dae8205ef265929c7eb43dca473

runtime: docker
arch: aarch64
client: v27.2.0
server: v24.0.7
limactl version 0.23.2
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)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

$ 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/user/.colima/default/docker.sock

Reproduction Steps

1. rm -rf ~/Library/Caches/colima/docker-certs
2. mkdir -p ~/.docker/certs.d (you don't actually need a cert in this directory to make the warning happen)
3. colima start

Expected behaviour

Creation and removal of the cache directory should be automatic and graceful.

Additional context

Looks like this PR likely introduced the regression:
#1112

Should probably by rm -rf or conditioned upon the existence of the directory.