<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Stage Build on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/multi-stage-build/</link><description>Recent content in Multi-Stage Build on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 18 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/multi-stage-build/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (3): Dockerfile Patterns — From Naive to Production</title><link>https://www.chenk.top/en/docker-containers/03-dockerfile-patterns/</link><pubDate>Sun, 18 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/03-dockerfile-patterns/</guid><description>&lt;p>Most tutorials show you a 5-line Dockerfile and move on. When you deploy to production, you might find your image is 1.2 GB, builds take 8 minutes even for a one-line code change, and your security team flags vulnerabilities in packages you didn&amp;rsquo;t know were installed. Writing a good Dockerfile is a skill that pays off every time your CI pipeline runs.&lt;/p>
&lt;hr>
&lt;h2 id="every-dockerfile-instruction" class="heading-anchor">Every Dockerfile Instruction&lt;a href="#every-dockerfile-instruction" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Let&amp;rsquo;s go through every instruction you&amp;rsquo;ll use, with concrete examples.&lt;/p></description></item></channel></rss>