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
At the moment, podman machine has several expectations about what the VM image will be doing/providing:
ssh is running and private key/username to connect over ssh are known
when booting is done, a "ready" notification is sent from the guest to the host
ignition is used to configure the VM image. podman-machine uses this to inject ssh keys for 1) and systemd units for 2)
is a particularly strong assumption as the ssh connection details are passed to gvproxy on the command line to proxy a unix socket over an ssh tunnel. When these args are on the command line, if gvproxy did not manage to establish a ssh connection in a few minutes, it will exit. This means the VM will lose all its networking.
We need to make all of these optional
The text was updated successfully, but these errors were encountered:
At the moment, podman machine has several expectations about what the VM image will be doing/providing:
ssh is running and private key/username to connect over ssh are known
when booting is done, a "ready" notification is sent from the guest to the host
ignition is used to configure the VM image. podman-machine uses this to inject ssh keys for 1) and systemd units for 2)
is a particularly strong assumption as the ssh connection details are passed to gvproxy on the command line to proxy a unix socket over an ssh tunnel. When these args are on the command line, if gvproxy did not manage to establish a ssh connection in a few minutes, it will exit. This means the VM will lose all its networking.
We need to make all of these optional
The text was updated successfully, but these errors were encountered: