CoreOS Launches Rkt 1.0 (eweek.com)
darthcamaro writes: Docker is about to get some real competition in the container runtime space, thanks to the lofficial aunch of rkt 1.0. CoreOS started building rkt in 2014 and after more than a year of security, performance and feature improvement are now ready to declare it 'production-ready.' While rkt is a docker runtime rival, docker apps will run in rkt, giving using a new runtime choice: "rkt will remain compatible with the Docker-specific image format, as well as its own native App Container Image (ACI). That means developers can build containers with Docker and run those containers with rkt. In addition, CoreOS will support the growing ecosystem of tools based around the ACI format."
I spin up a new Windows server as a virtual machine, play around, revert as needed, and destroy it.
This is slow... SUPER slow...
At Mozilla we are starting to use docker for running linux tests... We can reset a container to initiate state and run the next task in a second or so... This means we don't spend time bring up/down VMs... and every test or build task has a clean environment..
Also we don't need to rebuild AMI when updating a dependency like gcc (if say we want to build against a new version)
For the server stuff where I've played with docker... the main benefit is that it's a lot easier to build and move images.. Building and testing AMIs locally is a special kind of pain I wouldn't care to entertain. Also you can deploy docker images in any cloud.
Note: I prefer immutable infrastructure, so docker is really killer as copy-on-write makes it quick to start a container from clean state.