Verify a container that can't be accessed via SSH

[walterdolce]

I just came across a use case whereby I have a container which hasn't got SSH or anything inside. The container image in question is Grafana's (5.2.2).

The workflow is currently as follow:

• Use kitchen-docker as driver
• During kitchen create, kitchen-docker will pick up a custom Dockerfile (via its dockerfile config param).
• After kitchen create, the container is ready (there really is no need for provisioning anything here as everything happens when the container is built. In fact, the provisioner configured in .kitchen.yml is currently set as dummy).
• Run kitchen verify, which will use kitchen-inspec.

But the following issues occur:

• kitchen-inspec uses the SSH transport by default. But there's no SSH of sorts. The container is SSH-less.
• kitchen-inspec can't be configured to be used the docker transport (aka backend). Add ability to specify 'backend' in runner options #196 supports this cause in addition to the one specified in there.
• test-kitchen can't be configured to having a transport: docker. It would error saying a gem/library is needed.

While #196 gets some attention, what do you think would be the best thing to do here?

Thank you.