Persistent Storage for Docker Containers

Docker has made persisting data in a container environment easier by supporting storage plug-ins, which can be used to to dynamically create, attach, and delete volumes. However, Docker is facing pressure to move enterprise data storage features upstream into its platform, similar to pressures OpenStack has faced. Docker should resist the pressure and opt instead to keep things simple for users.

The evolution of the next generation data center continues to accelerate

Just a few short years ago, “cloud” was all the buzz; some people got on board early, while some waited until it was viewed as more “mainstream.” Make no mistake: I love cloud and OpenStack, and I loved the vision it had for the future of the data center.

We used to talk about things like cloud native, scale out, and ephemeral, and for some, it really resonated. At the same time, however, cloud became a bit, well, cloudy. It sort of lost its identity and started trying to cater to any and all applications and use cases. In other words, it wants to be all things to all people. That’s great — nothing wrong with it. And the fact is that not everybody is ready or able to reinvent how they do things and throw away their existing investments.

Now, let’s consider the latest phenom in the IT industry. Some of you may remember it as chroot, others maybe as jails. Regardless of what it started as, or even when it started, chances are more likely than not you’ve heard of containers and Docker. I’m not going to go into Docker and what’s cool about it or what the use cases might look like. Instead, I want to focus on one small component of Docker and give my view on what’s good about it. That one little feature, if you haven’t already guessed, is persistent storage (aka “volume plug-ins”).

To read more of this article, please sign up to join the SolidFire learning center.

Sign up
request a demo
contact sales