RFE: crc cleanup

[opuk]

It would be nice to have a command like crc cleanup or crc uninstall which cleans up everything that crc setup creates, for example libvirt networks.

[gbraad]

crc cleanup sounds like clearing a/the cache, and crc uninstall sounds like a removal tool. we try to keep our footprint as small as possible (like placing dependencies inside our homedir), but you rae right. We have to look into this and come up with a solution to make this clear or either reduce even more needed setup steps.

[d-laing]

+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).

• Delete the existing .crc directory from my home directory (otherwise, I got an error when running crc start)
• Delete the existing crc VM from Virtual Machine Manager (perhaps this step would be self-evident for some users)

Many thanks.

[cfergeau]

@laidan6000 crc delete would probably have been enough in your situation. However, this bug is about something different. Schematically, crc delete removes what crc start created, this bug is about removing the changes that crc setup did.

[d-laing]

Oh! I didn't think to run crc delete before attempting to setup and start the new version. Thanks for the information!

[gbraad]

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> .

[d-laing]

Yes, I had a VM from the alpha release. I got a "missing bundle" error when attempting to start CRC.
Thanks for the assistance.

[cfergeau]

I think this is a duplicate of #348

[praveenkumar]

@cfergeau #348 is for adding extra net around checking the content we download like oc or machine driver (if the sha doesn't match), this issue more like exposing a clean command for user to unset all the configuration which we did as part of setup command and also remove ~/.crc folder.

[cfergeau]

I'm not quite sure what #348 is about to be honest, I'm confused by the wording.

[stale]

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.

[dlewis7444]

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.

[anjannath]

Fixed via #651 #1153 #1155

[cfergeau]

At this point this is only partially fixed (libvirt group changes on linux for example are not undone).

[planetf1]

+1 for a full cleanup - I seem to have fallen into a trap with bad network config I am unpicking manually

[anjannath]

@cfergeau Ahh, right, do you want to keep this issue open, or create a new one, with the remaining things.

[gbraad]

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 ]