<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Fábio C. Barrionuevo da Luz</title>
    <description>The latest articles on DEV Community by Fábio C. Barrionuevo da Luz (@luzfcb).</description>
    <link>https://dev.to/luzfcb</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F347077%2F70584a6c-3c51-48f5-b7f2-7be536ebd366.jpeg</url>
      <title>DEV Community: Fábio C. Barrionuevo da Luz</title>
      <link>https://dev.to/luzfcb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/luzfcb"/>
    <language>en</language>
    <item>
      <title>A quick way to detect bad practices on a Dockerfile</title>
      <dc:creator>Fábio C. Barrionuevo da Luz</dc:creator>
      <pubDate>Tue, 28 Apr 2020 17:08:40 +0000</pubDate>
      <link>https://dev.to/feldroy/a-quick-way-to-detect-bad-practices-on-a-dockerfile-41dl</link>
      <guid>https://dev.to/feldroy/a-quick-way-to-detect-bad-practices-on-a-dockerfile-41dl</guid>
      <description>&lt;p&gt;In Feldroy we use Docker images as the base to running the tools to build the PDF, EPUB, and Kindle files from the content written by &lt;a class="comment-mentioned-user" href="https://dev.to/audreyfeldroy"&gt;@audreyfeldroy&lt;/a&gt;
 and &lt;a class="comment-mentioned-user" href="https://dev.to/danielfeldroy"&gt;@danielfeldroy&lt;/a&gt;
.&lt;/p&gt;

&lt;p&gt;Having a 100% functional Dockerfile that follows good practices is a good thing to have.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://hadolint.github.io/hadolint/"&gt;&lt;code&gt;hadolint&lt;/code&gt;&lt;/a&gt; is a linter tool that helps to validate a Dockerfile to build Docker images that follow the recommendations of the &lt;a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices/"&gt;&lt;code&gt;Best practices for writing Dockerfiles&lt;/code&gt;&lt;/a&gt; guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick way to use
&lt;/h2&gt;



&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;docker run --rm -i hadolint/hadolint &amp;lt; Dockerfile
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;h2&gt;
  
  
  What is the validation rules
&lt;/h2&gt;

&lt;p&gt;The validation follows these rules: &lt;a href="https://github.com/hadolint/hadolint#rules"&gt;https://github.com/hadolint/hadolint#rules&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to customize the validation
&lt;/h2&gt;

&lt;p&gt;We can customize the validation by creating the &lt;code&gt;.hadolint.yaml&lt;/code&gt; file: &lt;a href="https://github.com/hadolint/hadolint#configure"&gt;https://github.com/hadolint/hadolint#configure&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to integrate on the CI Server
&lt;/h2&gt;

&lt;p&gt;There are several examples of how to use &lt;code&gt;hadolint&lt;/code&gt; on &lt;code&gt;CI servers&lt;/code&gt;: &lt;a href="https://github.com/hadolint/hadolint/blob/master/docs/INTEGRATION.md"&gt;https://github.com/hadolint/hadolint/blob/master/docs/INTEGRATION.md&lt;/a&gt;&lt;/p&gt;

</description>
      <category>todayilearned</category>
      <category>docker</category>
      <category>dockerfile</category>
      <category>lint</category>
    </item>
  </channel>
</rss>
