So are the docs out of date, or does Docker still not use user namespaces? This was promised quite a while ago and has slipped multiple versions so far, and it's a lot more important to serious uses of Docker than `docker cp`.
This is a cheap shot and has no basis in the reality of how open source projects are managed and how people contribute to them.
The literally-literally most important security concern in containerland, not allowing container escapes to have host root, is not done by Docker. But `docker cp` is, built at least in part by people working for Docker-the-company (I went and looked to be sure). So you can call it a cheap shot, and that's fine, but this is something promised a long time ago and my concern is for the people who buy the hype because they don't know any better, not the people generating it and should.
Certainly, it will take time to battle-test anything, so the sooner that feature has been released, the sooner that we can get started doing the battle-testing.
It would be helpful to have a clearer roadmap for features like this.
I've been putting docker off cause of coreos rockt vs docker and the security problem.
Was looking for alternative such as MirageOS and unikernel.
Since it seems like Docker and CoreOS have settle their issue now I'm waiting on security.
I think my only complaint about Joyent is their storage and services seem to be quite a bit more expensive than with Azure or AWS.