Docker Container Anti Patterns

I read &quot;anti-patterns&quot; but then it lists a lot of good things to do, with a few anti-patterns mixed in.<p>Fix the bold to be patterns or anti-patterns, not both, or change the title to be something like lessons learned.

&gt; Don’t use different images, or even different tags in dev, test, staging and production environment.<p>Can anyone comment on this? For example, many node projects have a list of devDependencies that have no use in production, so we build 3 images:<p>1. A base image with basically `NODE_ENV=production npm install`<p>2. A test image from the base with `NODE_ENV=development npm install`<p>3. A production image from step 1 with the CMD set.<p>Is this part of an &quot;anti-pattern&quot;? I thought it was how you&#x27;d get efficiently sized images in this situation.<p>(And yes, now that I write this I realize there only needs to be 2 images, the production one, and the test image is built from that)

&gt; Data or logs in containers<p>Instead of volume mapping like the article suggested, why not just log to stdout?