<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker on Sander Knape</title>
    <link>https://sanderknape.com/tags/docker/</link>
    <description>Recent content in Docker on Sander Knape</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 17 Jun 2019 13:30:02 +0200</lastBuildDate>
    <atom:link href="https://sanderknape.com/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Installing private Git repositories through npm install in Docker</title>
      <link>https://sanderknape.com/2019/06/installing-private-git-repositories-npm-install-docker/</link>
      <pubDate>Mon, 17 Jun 2019 13:30:02 +0200</pubDate>
      <guid>https://sanderknape.com/2019/06/installing-private-git-repositories-npm-install-docker/</guid>
      <description>&lt;p&gt;How do you properly use an SSH key in a Dockerfile? There are many ways to do it, including many ways to do it wrong. What you will want to prevent is that your ssh key ends up in one of your intermediate images or layers. These are the layers that Docker creates with pretty much every command in your Dockerfile. You may think that you properly clean up your secrets later in the Dockerfile, but the secret will then still be available in one of these layers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
