What's new in Docker 1.13: prune, secrets, checkpoints and more

I&#x27;m really looking forward to seeing the scientific community adopt docker as a way to distribute reproducible research and coursework.<p>MIT 6.S094 has a Dockerfile[^1] that contains all the software required for taking part in the class. This is a huge boon for getting stuck into the class and its coursework.<p>[^1]: <a href="http:&#x2F;&#x2F;selfdrivingcars.mit.edu&#x2F;files&#x2F;Dockerfile" rel="nofollow">http:&#x2F;&#x2F;selfdrivingcars.mit.edu&#x2F;files&#x2F;Dockerfile</a>

I&#x27;m just a guy that wants to deploy web apps. Is docker overkill for me? Basically, I want to be able to test something on my local machine under the same conditions it will be running on my server. Containerisation seems like the only way to do this that doesn&#x27;t involve keeping packages and system configurations in sync in two or more systems.

Does this mean the qcow2 disk space usage in Mac is fixed?

As much as I welcome the CLI cleanup, I can&#x27;t stop thinking that the &#x27;docker ps -&gt; docker container ls&#x27; change makes no sense to anyone who has any experience with bsd&#x2F;unix&#x2F;linux systems. Seriously, why?

Secrets is a big one! Will really help speed up enterprise adoption.

Looks like there&#x27;s a mistake about image pruning:<p>&quot;Add -f to get rid of all unused images (ones with no containers running them).&quot;<p>But the option is actually `-a` -- `-f` just simply skips the prompt.

Prune seems not that well thought to me. Don&#x27;t get me wrong, I do find it useful but many people use containers as environments. Think about how many people are going to run prune only to find their work go missing.<p>If you are gonna add a nuclear button, do it with a big red alert and give the option to whitelist some containers.

Curious what methods others use for handling secrets at build time (using docker-compose). I&#x27;m currently installing (private) dependencies at runtime by mounting my secrets as a volume. I couldn&#x27;t find a method that didn&#x27;t seem to have some risk of inadvertently exposing them.

Why not one &#x27;prune&#x27; command with &#x27;containers&#x27;, &#x27;images&#x27;, ... as an argument &#x2F; subcommand?<p>Would have seemed more intuitive to me.