http://blog.docker.com/2014/10/docker-1-3-signed-images-process-injection-security-options-mac-shared-directories/

 

Big highlights for container authors to pay attention to in this are around Docker Exec.  From the post:

 

Next, when developing an application, you sometimes need to look at it while it’s running.  A number of tools, like nsinit and nsenter, have sprung up to help developers debug their Dockerized apps, but these are additional tools to find, learn, and manage.  Similarly, some users have taken to running an init process to spawn sshd along with their app to allow them access, which creates risk and overhead.

 

To make debugging easier, we’re introducing docker exec, which allows a user to spawn a process inside their Docker container via the Docker API and CLI.  For example…

 

$ docker exec ubuntu_bash -it bash

 

…will create a new Bash session inside the container ubuntu_bash.

 

To be clear, by providing this we’re not changing our recommended approach of “one app per container.”  Instead, we’re responding to users who’ve told us they sometimes need helper processes around the app. That’s what `docker exec` is about.

Very cool to have that built in to Docker itself! And liking the screenshot too :0

This is a a really bug deal and fixes one of the shortcomings of Docker. Perfect timing.

Nice! Now if they add in process  management then no other tools would be required