allow to run integration test without docker

[theko2fi]

The integration tests run by default inside a docker container. It would be nice if this behavior could be overrided by the user. I mean, an option to choose if we want to run with docker or not. I would like to run directly on the runner host.

Thanks !

[webknjaz]

Thanks for filing the issue! This action is currently aimed at providing seamless and reproducible workflow and using docker is what makes it possible. We don't currently plan to allow running it in an arbitrary environment.
However, if you need to do so for some reason, you can pip install ansible-core and call ansible-test manually with any arguments you like. I think this would be the way to go anyway, since you're opting to maintaining your in-job setup details more flexibly and would already be reproducing what this action does in your job definitions.

Though, may I ask why you think you need to avoid using docker?

[theko2fi]

Thanks for your feedback! You're right, I will go that ansible-test way like I used to do. I just learned about GitHub actions modules and wanted to give it a try.

I'm not trying to avoid using docker, I love it. But right now, I'm developing an Ansible collection for . Multipass is similar to Vagrant, it helps you quickly spin up Ubuntu virtual machines on your host. My Ansible collection will contain modules and connection plugin to connect and manage (create, delete...) multipass VMs. So my integration tests need to run directly on the runner host, since VM can't be created inside docker containers.

[webknjaz]

That's an interesting case. I wonder if putting docker on the same network would help access multipass from within a container. Can its daemon listen to a TCP/IP socket rather than a file socket?