Add attempt to connect to socket before selecting it as runtime

[eharris128]

What

• Ping sockets before designating it as runtime

Why

• crt.AutoRuntime would tell the tui -> i images OnCommand invocation to use containerd as runtime. However, the application could not talk to this containerd socket due to permission issues. The socket was there from the perspective of Stat - but this did not guarantee sufficient access to communicate with the socket.

How Tested

mint images
mint tui -> i

New Experience

• When a user's environment has podman & containerd, but the application does not have sufficient permissions to access these sockets, then fallback to docker:
  

[kcq]

Yes, it is a good idea to check if the default/assumed runtime (when no explicit runtime param is specified) is available. A wishlist enhancement :-)

[eharris128]

A future TODO

[kcq]

@eharris128 there might be another bug to investigate there... The "auto crt" logic shouldn't have picked containerd unless containerd is the only thing is installed. What's the docker socket you have in your environment? What's the docker context info?

[eharris128]

What's the docker socket you have in your environment? What's the docker context info?

Will share these details next time I am on my dev machine.

[eharris128]

@kcq

[kcq]

@eharris128 can you also run docker context ls and ls -lh /var/run/docker.sock

[kcq]

Either way, the /var/run/docker.sock socket should have been picked by the auto container runtime selection logic. With the Docker runtime detection it's supposed to go through these three stages:

1. Try using the unix socket from docker context
2. If there's no docker context configured try using /var/run/docker.sock
3. Try using the user directory located docker socket (usually from Docker Desktop installs)

[eharris128]

@kcq very delayed here, but I ruined the reproducibility as I upgraded to Ubuntu 24 LTS last week (in order to work with Podman - as the Ubuntu 22 LTS's installation of Podman does not work for mint).

With the Ubuntu 24 LTS default docker configuration, we no longer get the issue of defaulting to containerd (when docker is installed).

[kcq]

@eharris128 no worries :) can you create a GitHub issue with the notes from our discussion about it