-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: crc cleanup #507
Comments
|
+1 to this RFE. For information, I needed to perform some extra tasks to successfully upgrade to the latest version of Code Ready Containers (crc-linux-1.0.0-beta.3-amd64).
Many thanks. |
@laidan6000 |
Oh! I didn't think to run |
Why did you have an existing VM? Likely you had an instance from the alpha,
but didn't start properly (like a missing bundle). That is a completely
different issue and already solved with delete as mentioned earlier.
…On Thu, Aug 29, 2019, 18:30 Daniel Laing ***@***.***> wrote:
Oh! I didn't think to run crc delete. Thanks for the information!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#507>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAAOZRF3W6ZO2AHW5CDJVTQG6QN7ANCNFSM4IR6VN5Q>
.
|
Yes, I had a VM from the alpha release. I got a "missing bundle" error when attempting to start CRC. |
I think this is a duplicate of #348 |
I'm not quite sure what #348 is about to be honest, I'm confused by the wording. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bad stalebot! No soup for you! This Enhancement is really needed. CRC modifies network settings. That's a bad thing for those of us that have heavily modified our network settings. |
At this point this is only partially fixed (libvirt group changes on linux for example are not undone). |
+1 for a full cleanup - I seem to have fallen into a trap with bad network config I am unpicking manually |
@cfergeau Ahh, right, do you want to keep this issue open, or create a new one, with the remaining things. |
I would suggest to collect a list of items that still need to be done. This
is independent of the issue being closed or a new one created.
For Windows we need to provide optional fixes, like the removal of the
vswitch (crc) (although we do not create), the removal of the Hyper-V
feature, etc
…On Mon, Apr 20, 2020 at 7:08 PM Anjan Nath ***@***.***> wrote:
@cfergeau <https://github.com/cfergeau> Ahh, right, do you want to keep
this issue open, or create a new one, with the remaining things.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#507 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAOZUQESZC3E5HKKXY7ULRNQUJDANCNFSM4IR6VN5Q>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
It would be nice to have a command like
crc cleanup
orcrc uninstall
which cleans up everything thatcrc setup
creates, for example libvirt networks.The text was updated successfully, but these errors were encountered: