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
Currently, when they have a preexisting VM, and then upgrade the crc
binary, the user will experience various
misbehaviours:
1. if the binary embeds a bundle, `crc start` will complain that
~/.crc/crc_libvirt_4.1.9.crcbundle does not exist, and that `crc setup`
must be run first. Once that is done, `crc start` will unpack the
bundle, but will not make use of it since an older VM already exists.
2. if the binary does not embed a bundle, `crc start` will still expect
to be passed a bundle, and will uncompress it even if once again it's
not going to be able to use it
This commit uses the BundleName data which was added to
code-ready/machine in order to load the correct bundle
when starting a pre-existing VM, which solves both issues.
This fixes#438
0 commit comments