Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

"Dockerfiles Considered Harmful"

DZone's Guide to

"Dockerfiles Considered Harmful"

Why Dockerfiles should be avoided, especially in testing, for the good of your operations team.

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.

I found an interesting piece on the Wercker blog from Andy Smith, called "Dockerfiles Considered Harmful." I've been trying to learn more about Docker lately, and I thought this would be an interesting read for you all.

One interesting point I learned about Dockerfiles is that Dockerfiles was created at a time where there weren't many tools designed to work with Docker, but there are still plenty of people testing their code in Dockerfiles. This is a bad idea. 

Instead, Andy suggests using a Bash script instead, which would be more predictable and useful to most developers. 

Andy also goes more in-depth about layers, the registry, and several alternatives to using Dockerfiles, including avoiding registry use, using only one layer, restructuring your deployment lifecycle, and using tools designed for build/test/deploy.

You can read the article in full here. What do you think about it?

Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.

Topics:
devops ,docker ,testing

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}