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

Post by scanr » Tue, Jan 31, 2017, 12:58 PM UTC

lacampbell wrote: post #3

I'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't involve keeping packages and system configurations in sync in two or more systems.

    * You can be sure that what you're running locally 
      is exactly what you'll be running on the server
    * Your deployment experience will be the same 
      regardless of which tech stack you're using for the 
      web application
    * There are many places you can deploy docker 
      containers (Google GCE, Amazon ECS, Amazon EB, etc.)
    * A web application is often composed of several 
      services (e.g. the web app, a database, redis etc.) 
      and docker compose makes it easy to fire all of 
      those up in development e.g. if a new 
      developer joins, they only need to install 
      docker rather than web app framework + 
      database + redis
    * Docker sets you up quite well to grow into a 
      more complex deployment (e.g. using Kubernetes)

Post by RabbitmqGuy » Tue, Jan 31, 2017, 1:43 PM UTC

kingrolo wrote: post #17

akavel wrote: post #15

Earlier quoted context omitted.

What about docker-compose? We've recently started using it, and we don't see any problems; did your colleagues evaluate it?

docker-compose is really straightforward to get running, even moreso with docker-machine, and it gives you dev/prod parity, but the downside is that there's not a built in way to do zero downtime deploys.

Post by e40 » Tue, Jan 31, 2017, 1:46 PM UTC

realPubkey wrote: post #14

willemmali wrote: post #9

Earlier quoted context omitted.

Like this? docker rmi -af I'm a bit confused by the backticks as I use them all the time scripting, but also in Markdown.

I have a gist for it: https://gist.github.com/pubkey/73dcb894cf5f7d262863 #stop and delete all containers docker rm -f $(docker ps -a -q) #delete all images docker rmi -f $(docker images -q)

Post by bpicolo » Tue, Jan 31, 2017, 1:58 PM UTC

RabbitmqGuy wrote: post #23

kingrolo wrote: post #17

Earlier quoted context omitted.

docker-compose is really straightforward to get running, even moreso with docker-machine, and it gives you dev/prod parity, but the downside is that there's not a built in way to do zero downtime deploys.

Actually with the new docker-compose version 3 you can do rolling updates[1]. 1. https://docs.docker.com/compose/compose-file/#/deploy

Post by joekrill » Tue, Jan 31, 2017, 2:14 PM UTC

andmarios wrote: post #26

Prune seems not that well thought to me. Don'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. If you are gonna add a nuclear button, do it with a big red alert and give the option to whitelist some containers.