You can clone with
HTTPS or Subversion.
I've been digging around the internets and I can't find any information on this.
Can someone please tell me how to uninstall boot2docker on osx?
Was asking myself the same today. Looking at the source (https://github.com/boot2docker/osx-installer) I found boot2docker in the following locations, and deleted these.
Maybe a boot2docker guru can confirm these locations.
In addition, VirtualBox will be installed. If you're not using VirtualBox for anything else, you probably want to delete this as well. See: https://www.virtualbox.org/manual/ch02.html#idp50285088
Maybe an uninstall option would be great to have implemented in the installer?
I found these files too
+1 +infinity... boom.
In addition to what is listed above, I have:
/User/skyl/Library/Saved Application State/com.apple.ScriptEditor.id.boot2docker.savedState
I guess the last two are homebrew-related and not to be uninstalled. Not sure about the first two.
+1 Especially since it's borked after a Files & Settings transfer to a new machine.
+1. Please do this for Windows too.
There's a PR for this now: boot2docker/osx-installer#71
@naomik I included the files you found in my commit huangsam/osx-installer@e6b110f. @SvenDowideit, Are there any other files/processes I am missing before you merge the PR?
@huangsam hopefully @tianon will come by and review it, as he's the boot2docker lead now.
Does this also cover Windows installations?
why would it? the windows installer has (iirc) always had an uninstaller built by innosetup. (and you need to use the standard windows unintall UIs
@SvenDowideit doh! Stupid. Thought I had seen someone looking for ways to remove leftovers/traces on Windows as well, but a) that was probably another ticket and b) yes, of course there's the uninstaller.
That other PR is merged now.
Great work !
Everyone's +1's made something happen and stuff !
Everyone should feel proud and have a great day.
Is this available under the installer pkg right now? or should compile boot2docker from source on OSX to get uninstaller? I installed 1.3 version and I could not find uninstaller.
Whenever the uninstaller commits do find their way into the OSX installer release, I'd like to put a request inclusion in docker docs http://docs.docker.com/installation/mac/
@sindhus awesome suggestion - would you like to make a pull request?
Arrived at this thread when searching for a boot2docker uninstaller. I don't see anything on the OS X installation page referenced by sindhus about uninstalling and the installer 1.4.1 installer seems to go right into the installation.
I installed boot2docker via the installer before I realized there was a homebrew Formula. So now I'd like to uninstall and reinstall with homebrew. Any advice for a docker newbie?
@cimbriano the boot2docker uninstaller for OS X can be found here; https://github.com/boot2docker/osx-installer/blob/master/uninstall.sh
However, (afaik) the installer is the preferred way to install boot2docker on OS X; The homebrew formula is not maintained by boot2docker itself and uses the boot2docker-cli (see source) script which will be deprecated in the near future (see the boot2docker-cli README).
So, unless you have a strong reason to use homebrew instead, I'd stick with the official installer.
Hope this helps!
i would like to start boot2docker from scratch. After starting cisco anyconnect and frying it completely ( I understand that clugy routes can be applied, however, this is a mess especially when conveying it to others). Looking for a decent reset here.
@connaryscott docker-machine may be worth a look. I've found it to be a super-easy way to setup and teardown local boot2docker VMs:
docker-machine create -d virtualbox dev1
docker-machine create -d virtualbox dev2
docker-machine upgrade dev1
docker-machine rm dev2
# and so on... see: docker-machine help
When using the virtualbox driver, docker-machine uses (and automatically downloads) the boot2docker iso. I much prefer working with boot2docker in this way as I don't have to think about the particulars of installing, removing or upgrading it.
I cooked up some aliases and a bash function for simple toggling of the "active" machine and its DOCKER_... env variables:
Thanks for the tip will investigate...