<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tomoya Amachi on Medium]]></title>
        <description><![CDATA[Stories by Tomoya Amachi on Medium]]></description>
        <link>https://medium.com/@tomoyaamachi?source=rss-5861339d23d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-tvjRalJNBitCee8.</url>
            <title>Stories by Tomoya Amachi on Medium</title>
            <link>https://medium.com/@tomoyaamachi?source=rss-5861339d23d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:22:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomoyaamachi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The One Thing You Should Do After Building Best-Practice Docker Image (in 3 minutes)]]></title>
            <link>https://medium.com/@tomoyaamachi/the-one-thing-you-should-do-after-building-best-practice-docker-image-in-3-minutes-edc31336d1b6?source=rss-5861339d23d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/edc31336d1b6</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Tomoya Amachi]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 14:08:53 GMT</pubDate>
            <atom:updated>2019-06-19T14:08:53.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*9noe2FuFfSHN7x81bgXDYw.png" /></figure><h3>Overview</h3><p>Today, many companies tried to use Docker. This article is for wrote/writing <a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices/">best-practice Dockerfiles</a>.</p><p>I created a tool analyzes your Dockerfile via the built image in 3 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/0*eWMXNwDLL4HVHxRW.png" /></figure><blockquote><a href="https://github.com/goodwithtech/dockle"><em>Dockle — Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start</em></a></blockquote><p>Dockle is able to check deeply. (file permissions, credential files…) So, Dockle the best tool to check important rules, especially for security.</p><p>(I’m also the main committer of <a href="https://github.com/future-architect/vuls">Vuls</a> and <a href="https://github.com/knqyf263/trivy">Trivy</a>. These are famous vulnerability scanners.)</p><p>It’s <strong>NOT</strong> a Dockerfile Linter (like a hadolint).<br>It’s able to check security risks on a container base image too. Dockerfile Linter never does it.</p><p><a href="https://github.com/goodwithtech/dockle">I hope you star it!</a></p><p>OK, Let’s start!</p><h3>How to use</h3><h4>Homebrew (<a href="https://brew.sh/">Mac</a> / <a href="https://docs.brew.sh/Homebrew-on-Linux">Linux</a>)</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4ed7128f9023e83da8b8cb9625335f5c/href">https://medium.com/media/4ed7128f9023e83da8b8cb9625335f5c/href</a></iframe><h4>Linux</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb11c1015203c99eb4f170a8b3c1713f/href">https://medium.com/media/bb11c1015203c99eb4f170a8b3c1713f/href</a></iframe><h4>Windows</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e49520420812049a389e87e00d89dd1f/href">https://medium.com/media/e49520420812049a389e87e00d89dd1f/href</a></iframe><h4>via Docker</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/90f8b6875fb5727cd1e36afb8028d7a2/href">https://medium.com/media/90f8b6875fb5727cd1e36afb8028d7a2/href</a></iframe><p>You only need <em>-v /var/run/docker.sock:/var/run/docker.sock</em> when you’d like to scan the image on your host machine.</p><h3>Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRRSzG5pKJTzka-Rp1NdmA.png" /></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8920087dc9c0ef42b8871c1459228314/href">https://medium.com/media/8920087dc9c0ef42b8871c1459228314/href</a></iframe><p>This tool checks <a href="https://www.cisecurity.org/benchmark/docker/">CIS Benchmarks</a> and <a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices/">Best practices for writing Dockerfiles </a>.</p><p>Dockle shows short messages suggestions for improvement when there are problems.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/73c7db698275590638448aa266a5ac59/href">https://medium.com/media/73c7db698275590638448aa266a5ac59/href</a></iframe><p>You can check details to searching analysis codes(CIS-DI-0001...) on <a href="https://github.com/goodwithtech/dockle#checkpoint-detail">README</a>.</p><p>You don’t mind if your image doesn’t pass checkpoints. It’s one of an indicator.</p><p>Sometimes you have to run as root.<br>Sometimes CLI tool doesn&#39;t need HEALTHCHECK.<br>Sometimes use ADD statement when you&#39;d like to add tar files.</p><p>This is a reminder that really you’d like to do so.</p><p>You can be specified to ignore rules to give --ignore, -i option or create .dockleignore.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc19a173a6d46df8bc99ced54c6efbc1/href">https://medium.com/media/bc19a173a6d46df8bc99ced54c6efbc1/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0155146e72b740f9af8cfa33e809986/href">https://medium.com/media/a0155146e72b740f9af8cfa33e809986/href</a></iframe><p>Let’s do it again.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b271d6e6a363e12418bf0d16889682c/href">https://medium.com/media/4b271d6e6a363e12418bf0d16889682c/href</a></iframe><h3>Closing</h3><p>Dockle is <strong>NOT</strong> a Dockerfile Linter, but a Docker Image Linter.</p><p>Dockle can check deeply. (file permissions, credential files…) So, Dockle is able to check important rules than others, especially for security. (I’m also the main committer of <a href="https://github.com/future-architect/vuls">Vuls</a> and <a href="https://github.com/knqyf263/trivy">Trivy</a>. These are famous vulnerability scanners.)</p><p>And Dockle is able to analyze an image created by stdin, too. You could use it in many places.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc261730f28a1f831a32bc4a787dc6a6/href">https://medium.com/media/cc261730f28a1f831a32bc4a787dc6a6/href</a></iframe><p>I hope you like and <a href="https://github.com/goodwithtech/dockle">star it</a> !!</p><p>Thanks!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edc31336d1b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>