You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make crc and podman-machine closer, some changes will be needed in the way they use gvisor-tap-vsock. When crc starts its VM with podman-machine, bad things happen if the VM networking is handled by gvproxy while crc expects it to be done by the crc daemon (main issue is that the configured port forwarding, in particular for ssh won't work, as they will be set in the crc daemon, and not in gvproxy)
In order to make crc and podman-machine closer, some changes will be needed in the way they use gvisor-tap-vsock. When crc starts its VM with podman-machine, bad things happen if the VM networking is handled by gvproxy while crc expects it to be done by the crc daemon (main issue is that the configured port forwarding, in particular for ssh won't work, as they will be set in the crc daemon, and not in gvproxy)
/services
endpoint on the host in podman machine #19The text was updated successfully, but these errors were encountered: