diff options
| author | Burt Holzman <burt@fnal.gov> | 2022-03-23 10:42:05 -0500 |
|---|---|---|
| committer | Burt Holzman <burt@fnal.gov> | 2022-03-23 12:48:17 -0500 |
| commit | cdda1924a015fa1dc10a0e1231a9141884972640 (patch) | |
| tree | efe0550e18623c34fbec0747c6028316461f07c1 /cmd/podman/root_test.go | |
| parent | f049cba47c31d31a4a8ed9a9180f0e847be3411c (diff) | |
| download | podman-cdda1924a015fa1dc10a0e1231a9141884972640.tar.gz podman-cdda1924a015fa1dc10a0e1231a9141884972640.tar.bz2 podman-cdda1924a015fa1dc10a0e1231a9141884972640.zip | |
Explicitly use IPv4 to check if podman-machine VM is listening
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 ...".
[NO NEW TESTS NEEDED]
Signed-off-by: Burt Holzman <burt@fnal.gov>
Diffstat (limited to 'cmd/podman/root_test.go')
0 files changed, 0 insertions, 0 deletions