Originally created by @ppazos on GitHub (Mar 3, 2024).
I went through the installation process for catalina, it ran OK. Then I turned off the VM and started it again with the same command. Instead of booting from the installed one it started all over again, like the install didn't exist.
Should I go through half an hour of installation on each session using the VM? How can I persist the state of the VM?
Thanks.
Originally created by @ppazos on GitHub (Mar 3, 2024).
I went through the installation process for catalina, it ran OK. Then I turned off the VM and started it again with the same command. Instead of booting from the installed one it started all over again, like the install didn't exist.
Should I go through half an hour of installation on each session using the VM? How can I persist the state of the VM?
Thanks.
You have to restart your old image with docker start -ai xxxxxx where xxxxx is your container ID. You can find it using docker ps -a
@sickcodes commented on GitHub (Apr 8, 2024):
You have to restart your old image with `docker start -ai xxxxxx` where xxxxx is your container ID. You can find it using `docker ps -a`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ppazos on GitHub (Mar 3, 2024).
I went through the installation process for catalina, it ran OK. Then I turned off the VM and started it again with the same command. Instead of booting from the installed one it started all over again, like the install didn't exist.
Should I go through half an hour of installation on each session using the VM? How can I persist the state of the VM?
Thanks.
@sickcodes commented on GitHub (Apr 8, 2024):
You have to restart your old image with
docker start -ai xxxxxxwhere xxxxx is your container ID. You can find it usingdocker ps -a