A common problem with containerized applications is that their local storage is ephemeral, meaning that when the container goes away, so does its local storage. If you’re a fan of the 12 Factor methodology, then this won’t be a big deal because you’re storing your data in a much more rugged backing store (RDS, S3, etc). But, what if you’re dealing with a legacy application that expects to read/write from an NFS mounted filesystem? What if you’re adventurous and you really want to run your MySQL databases inside of a container? This makes sense for development environments, where development speed is much more important than being production-ready. However, even in the case of development environments, you’d love for your data to stick around. Let me show you an easy way to use Amazon’s EFS with Rancher to give your containers persistent storage. Read More
I’ve been playing with Docker and all of the associated tooling around that ecosystem for close to three years, but one of the things that’s always held me back was how hard the tools were to use. By itself, Docker doesn’t really do much to enable you to build highly reliable and scaleable systems. To fill this void, many high-profile projects have sprung up. You’ve probably heard the names Kubernetes, Mesos and Swarm, but most people are unaware of the very awesome, and very easy-to-use tool Rancher.