-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Drop intermediate container and use renaming instead #874
Comments
Why is this not gettin merged? |
I'm going to attempt a PR for this. What do you think about putting this into 1.3 milestone now that we're planning on requiring docker 1.6 ? |
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
PR Open at #1349 |
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
…. Will hopefully be fixed by docker/compose#874
the same problem with v1.5.1: version of docker-compose:
|
I did Or just |
I did |
With the merging of moby/moby#8570, Docker 1.5 will support container renaming. This means we can stop creating an "intermediate container" when recreating containers - their only purpose is to free up the container name while preserving volumes.
This will stop Compose working on Docker <1.5, but I think it's worth it: as well as generally reducing complexity, it'll remove the problem that #516 and #517 attempt to solve.
The text was updated successfully, but these errors were encountered: