This PR adds the ability to specify additional docker run arguments.
I have a use case where I am running tests that depend on a virtual CAN device configured on the host. In order for the tests to succeed, Docker must be executed with --net=host. I assume there are other scenarios where this could come in handy as well, e.g. add environment variables, mount volumes, etc.
The action's internal arguments can not be overridden by user config.
This PR adds the ability to specify additional
docker runarguments.I have a use case where I am running tests that depend on a virtual CAN device configured on the host. In order for the tests to succeed, Docker must be executed with
--net=host. I assume there are other scenarios where this could come in handy as well, e.g. add environment variables, mount volumes, etc.The action's internal arguments can not be overridden by user config.