Closed tianon closed 9 years ago
An example of how this looks:
$ ./boot2docker shellinit
WARNING: the 'boot2docker' command is officially deprecated.
Please switch to 'docker-machine' (https://github.com/docker/machine)
as soon as possible.
error in run: Failed to get machine "boot2docker-vm": machine does not exist (Did you run `boot2docker init`?)
Yeah, that looks pretty good. I think it might be more useful to link them to https://docs.docker.com/machine/ though. Would at least save them a click.
Looks good -- +1 for the link to the docs as that tends to be our recommended entry point.
Cool, that one's an easy fix. :+1:
Updated the upgrade
code to only download releases that match 1.x
or v1.x
, and removed the "Docker client upgrade" portion as that's likely to only cause pain in the future.
LGTM - can we also add a proposed EOL? (deprecation only starts a clock)
It might be worth recommending that users download Toolbox to install Machine. Nearly everyone using the boot2docker CLI will have got it from the installers, so Toolbox is the replacement from their POV.
/cc @moxiegirl @mchiang0610
SGTM
On Mon, Aug 10, 2015 at 2:03 PM, Ben Firshman notifications@github.com wrote:
It might be worth recommending that users download Toolbox to install Machine. Nearly everyone using the boot2docker CLI will have got it from the installers, so Toolbox is the replacement from their POV.
/cc @moxiegirl https://github.com/moxiegirl @mchiang0610 https://github.com/mchiang0610
— Reply to this email directly or view it on GitHub https://github.com/boot2docker/boot2docker-cli/pull/377#issuecomment-129551210 .
@bfirsh +1. Should I create a separate PR for this?
I'm not a big fan of the HTTP endpoint logic, but it's all in now. I also backed out the "> v1.x" exclusion, and I've merged Nathan's PR that includes the updated language mentioning Toolbox.
@SvenDowideit I think an explicit EOL date will convey that we're actually still supporting this up until that point, which is a disservice to our users IMO. We'll still "support" it, but it's going to get even less attention than it was before, so I think we're essentially saying that it's EOL today barring major or severe issues.
A screenshot of a chat totally counts as a LGTM, right? :smile:
LOL u devious
is it possible to create a light boot2docker wrapper for the docker toolbox? to facilitate migrating :D
like a boot2docker-cli-wrapper-docker-toolbox
alias boot2docker="..."
@cblage You might be able to set a bash function which "converts" b2d-cli commands to Docker Machine (e.g. boot2docker up
becomes docker-machine start default
) but it will likely be fragile and could potentially fall over in a variety of places.
This is a WIP and not ready for merge. DO NOT MERGE YET. This is being opened so we can discuss how to orchestrate and communicate the official deprecation properly, and how we'll manage the release of 1.8 to make sure users have a way to continue using this old code if they absolutely need to while still encouraging them very strongly to move off of it ASAP.
cc @ehazlett @nathanleclaire