Explicitly use IPv4 to check if podman-machine VM is listening

[holzman]

When starting a VM that has been configured with volume mounts, the podman client attempts to connect via
TCP to localhost, which runs gvproxy to proxy an ephemeral port to the VM's ssh port. Previously, gvproxy
was listening on all interfaces and IP addresses, but this behavior has changed to listening only on the
IPv4 loopback address.

Without this change, if a newer build of gvproxy is used, a podman machine configured with volume mounts
will hang forever after "podman machine start" with "Waiting for VM ...".

Signed-off-by: Burt Holzman [email protected]

[mheon]

LGTM

[mheon]

/approve

[rhatdan]

/approve
/lgtm
/hold

[Luap99]

If gvproxy only listens on 127.0.0.1, why not just replace localhost with 127.0.0.1 here.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: holzman, mheon, rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mheon,rhatdan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[holzman]

If gvproxy only listens on 127.0.0.1, why not just replace localhost with 127.0.0.1 here.

Either works (and is equally readable as far as I'm concerned). I can change it if reviewers prefer.

[Luap99]

I prefer 127.0.0.1 because AFAIK you could in theory change localhost to another ip but I guess in this case many things would break.

[Luap99]

You also have to add [NO NEW TESTS NEEDED] to your commit message.

[rhatdan]

/lgtm

[rhatdan]

/lgtm

[rhatdan]

/hold cancel