Skip to content
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

Bail out immediately if there are legacy containers #1441

Merged
merged 1 commit into from
May 26, 2015

Conversation

aanand
Copy link

@aanand aanand commented May 21, 2015

Sits on top of #1440.

If there are legacy containers, then in almost all cases it's not safe to keep doing whatever we were about to do. Additionally, the error output was pretty difficult to read.

I've changed it so we display a single message with all the names, plus directions for removing the containers if the user doesn't want to migrate, and then exit.

@aanand aanand force-pushed the abort-on-legacy-containers branch 2 times, most recently from bae72ad to a9cac7b Compare May 21, 2015 17:32
@aanand aanand modified the milestone: 1.3.0 May 21, 2015
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
@aanand aanand force-pushed the abort-on-legacy-containers branch from a9cac7b to 0b4d940 Compare May 26, 2015 10:53
aanand referenced this pull request in aanand/fig May 26, 2015
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
@dnephin
Copy link

dnephin commented May 26, 2015

LGTM

1 similar comment
@bfirsh
Copy link

bfirsh commented May 26, 2015

LGTM

bfirsh added a commit that referenced this pull request May 26, 2015
Bail out immediately if there are legacy containers
@bfirsh bfirsh merged commit 8af4ae7 into docker:master May 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants