Closed virtuald closed 6 years ago
Is it just a matter of updating where the various files reference either 1.3.0 or 1.3.2 to be 1.4.0 now? I would try it, but I don't want to corrupt my VM if I can avoid it...
Agreed, would be really good if the docker release were better coordinated so that boot2docker and "brew" are updated at the same time as the docker release announcement.
FYI I did a "boot2docker upgrade" and got docker 1.4, though my client on OSX is still 1.3.2. I'm not sure that's a supported configuration.
I also did a boot2docker upgrade and got a 1.4 ISO so now file sharing stopped working, probably cause of some VirtualBox / ISO version mismatch. I had to do;
boot2docker download --iso-url=https://github.com/boot2docker/boot2docker/releases/download/v1.3.3/boot2docker.iso
boot2docker init
to get everything up and running again.
This means that everyone following tutorials etc are failing and have no clue why examples are not working for them.
and would like to echo jamshid's point - coordinating the release of these things, including brew, would be a very nice thing.
@tianon ..
Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).
I note that the boot2docker iso has been upgraded to 1.4.0, but the installer hasn't yet?