Molecule with vagrant driver

[michalkonieczny91]

Hello, I'm trying to use molecule with vagrant driver but I'm still receiving an error
Failed to connect to the host via ssh: ssh: Could not resolve hostname instance: Temporary failure in name resolution

steps to reproduce:
molecule init scenario -d vagrant --dependency-name galaxy --provisioner-name ansible pure
It creates structure

.
├── converge.yml
├── create.yml
├── destroy.yml
└── molecule.yml

and then I do
molecule converge -s pure
and I have an error
fatal: [instance]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname instance: Temporary failure in name resolution", "unreachable": true}
To be honest parameters in init command are ignored and molecule.yml looks like this:

---
platforms:
  - name: instance
    # you might want to add your own variables here based on what provisioning
    # you are doing like:
    # image: quay.io/centos/centos:stream8

There is no indication to use vagrant
but even with an example from https://github.com/ansible-community/molecule-plugins/tree/main/doc/vagrant#documentation I'm receiving the same error the last thing what I tried is remove files:

├── create.yml
├── destroy.yml

but then I'm receiving an error
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "ERROR: Driver missing, install python-vagrant.\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
when command
molecule drivers returns me
╶──────────────────────────────────────────────────────────────────────────────────
azure
containers
default
docker
ec2
gce
podman
vagrant

I have checked molecule with docker driver, and it works without any problems

Additional info:

$molecule --version
molecule 6.0.3.dev7 using python 3.9 
    ansible:2.15.2
    azure:23.5.0 from molecule_plugins
    containers:23.5.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    default:6.0.3.dev7 from molecule
    docker:23.5.0 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0
    ec2:23.5.0 from molecule_plugins
    gce:23.5.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    podman:23.5.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    vagrant:23.5.0 from molecule_plugins

[gamblar13]

As I can see the support for the drivers (during init) has been removed... I can't imagine what idea is behind this.
See this commit: 21dcd2b

[marcinpraczko]

I still have the same problem, would be nice to have working driver for vagrant as is widely used. And not every solution can be tested on docker (or containers).

My current settings:

molecule 24.2.1 using python 3.11 
    ansible:2.15.6
    azure:23.5.3 from molecule_plugins
    containers:23.5.3 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    default:24.2.1 from molecule
    docker:23.5.3 from molecule_plugins requiring collections: community.docker>=3.4.11 ansible.posix>=1.4.0
    ec2:23.5.3 from molecule_plugins
    gce:23.5.3 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    openstack:23.5.3 from molecule_plugins requiring collections: openstack.cloud>=2.1.0
    podman:23.5.3 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    vagrant:23.5.3 from molecule_plugins

[bitozoid]

As suggested from IRC, I just removed the create.yml and destroy.yml templates created on init, and molecule used the corresponding driver playbooks. However, then I ran into ansible-community/molecule-plugins#239, where a workaround is proposed as well.