The current prepare-docker role (a prerequisite for testing roles that need installed docker) is made to connect to host docker daemon for container operations and requires access to host docker socket.
Sharing of docker daemon with underlying host system is considered as a potential problem for couple of reasons:

• problematic clean-up of tested docker containers
• At least one role under test (namely the "docker" role) requires being able to start docker directly, and in the current approach it is not possible without dirty hacks

There exists a role called prepare-docker-dind that just installs and starts docker normally and doesn't use host docker at all. This role is used for rke testing, and seems to work well.

proposed approach would be to unify&polish existing relevant roles

(prepare-docker & prepare-docker-dind)

and readjust all molecule tests to start using that DIND approach