Burt Holzman 8bc2f6cd84 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>		2022-03-30 15:36:05 -04:00
..
qemu	Explicitly use IPv4 to check if podman-machine VM is listening	2022-03-30 15:36:05 -04:00
wsl	Introduce podman machine init --root=t|f and podman machine set --root=t|f	2022-02-16 14:02:58 -05:00
config.go	MacOS improvements	2022-03-18 15:06:57 -05:00
connection.go	Introduce podman machine init --root=t|f and podman machine set --root=t|f	2022-02-16 14:02:58 -05:00
fcos.go	Temporarily pull machine images from side repo	2022-02-14 15:10:40 -06:00
fedora.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00
ignition.go	MacOS improvements	2022-03-18 15:06:57 -05:00
ignition_darwin.go	Set machine timezone	2021-12-16 12:40:20 -06:00
ignition_linux.go	Set machine timezone	2021-12-16 12:40:20 -06:00
ignition_schema.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00
ignition_windows.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00
keys.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00
machine_unsupported.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00
pull.go	Introduce Windows WSL implementation of podman machine	2021-12-24 19:28:10 -06:00