I don't understand why add another domain-specific command to a container manager and go out of scope for what the tool was designed for at first place.
replies(3):
It's fine to disagree of course, but we envision Docker as a tool that has a higher abstraction level than just container management. That's why having a new domain-specific command (that also uses domain-specific technology that is independent from containers, at least on some platform targets) is a cohesive design choice from our perspective.