Description

When trying different configurations of a runtime, it becomes handy to have a way to the runtime's specific configuration file.
Nowadays, some runtimes work this around by distributing a shell script wrapping the call to their binaries, setting the configuration file as part of this shell script. Although this works, this could be simpler.

But how to solve this? I think we should take a look on what containerd does, which is basically adding an "option" field under the runtimes.$runtime configuration, where one can specify the ConfigPath.

This is an example of a containerd configuration that shows such a thing:

    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata-clh]
          runtime_type = "io.containerd.kata.v2"
          privileged_without_host_devices = true
          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata-clh.options]
            ConfigPath = "/etc/kata-containers/configuration-clh.toml

Note: I don't see this as a high priority feature, at all, but this is for sure a nice to have and also a good first issue for a newcomer.