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
Thank you so much for building this. This has been incredibly helpful.
I'm using this to spin up a Docker VM while I wait for Docker to become compatible with Apple Silicon. My VM seems to panic and shut down after a few minutes of pulling Docker images. The logs from vftool don't indicate any panics from AppleVZ, and screenlog.0 doesn't say anything before it shuts down, but I'm unable to find any instances of vftool in my process list after a few minutes.
Am I doing something wrong?
If it helps, I'm starting it on Ansible but am daemonizing it through nohup and shell redirection. The subshell running vftool forks from PID 1 when I do it this way.
The text was updated successfully, but these errors were encountered:
You should use screen to start the vm instead of nohup which is not suitable for job with tty output.
e.g.
screen -S vm # to start a screen with name vm
./vftool ... ... # to start the vm
After starting vm use Ctrl-A D to detach the screen.
screen -ls to list the screens
screen -r vm # to resume screen named vm
Thank you so much for building this. This has been incredibly helpful.
I'm using this to spin up a Docker VM while I wait for Docker to become compatible with Apple Silicon. My VM seems to panic and shut down after a few minutes of pulling Docker images. The logs from
vftool
don't indicate any panics from AppleVZ, andscreenlog.0
doesn't say anything before it shuts down, but I'm unable to find any instances ofvftool
in my process list after a few minutes.Am I doing something wrong?
If it helps, I'm starting it on Ansible but am daemonizing it through
nohup
and shell redirection. The subshell runningvftool
forks from PID 1 when I do it this way.The text was updated successfully, but these errors were encountered: