[Questions] related to the varlink server address format

[4383]

Hello,

Do you seen any reasons (that I maybe missed) to limit the client uri to a local path (i.e unix:/run/podman/io.podman)?

If I'm right varlink also accept tcp addresses (i.e tcp://127.0.0.1:38005) and in this case podman specifically ignore them.

• Do you you have any reasons to ignore this kind of address (tcp format)?
• Do you think that we could adapt this code to allow users to pass tcp format too?

To allow you to better understand our needs and why I ask these questions lets me explains a little bit our situation. I implemented a podman client in tobiko (a new testing framework for openstack) and tobiko establish an SSH connection to the openstack node (controller, compute, etc) and then it proxifying server connections through tcp to allow us to centralize SSH config and mechanismes in only one place.

For these reasons we prefer to pass through a proxified python-podman LocalClient and ssh/tcp rather than using a python-podman RemoteClient and a direct usage of SSH with python-podman.

Example with the code bellow:

from tobiko.shell import ssh
from tobiko.tripleo import overcloud

ssh_client = overcloud.overcloud_ssh_client('controller-0')
uri = 'unix:/run/podman/io.podman'
print(ssh.get_port_forward_url(ssh_client=ssh_client, url=uri))
# will print 'tcp://127.0.0.1:38005'

The previous code opened a SSH connection on the controller-0 of the openstack tripleo's overcloud and then we proxify the varlink connection through tcp by calling ssh.get_port_forward_url which will return the proxified podman's varlink server address and so, now, we would like to use it with a python-podman LocalClient and we facing the previous described python-podman's limitation.

I hope these infos help you to understand our use case.

For further reading you can also take a look to https://review.opendev.org/#/c/700527/

If you need more info do not hesitate to ask questions I will be happy to help you.