<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on Egor Lynko</title>
    <link>https://yegor.me/tags/docker/</link>
    <description>Recent content in Docker on Egor Lynko</description>
    <generator>Hugo -- 0.127.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 02 Oct 2022 20:00:00 +0200</lastBuildDate>
    <atom:link href="https://yegor.me/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Access private Git repository while building Docker image</title>
      <link>https://yegor.me/posts/access-private-git-repo-while-building-docker-image/</link>
      <pubDate>Sun, 02 Oct 2022 20:00:00 +0200</pubDate>
      <guid>https://yegor.me/posts/access-private-git-repo-while-building-docker-image/</guid>
      <description>&lt;p&gt;In this short article, I wanted to share two approaches to accessing private Git repositories
from within Dockerfile, while building Docker images. It can be useful to install dependencies
which are hosted in a private Git repo, like Ruby gems, NPM modules, you name it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Spoiler&lt;/strong&gt;: there is a &amp;ldquo;two-in-one&amp;rdquo; method described in the end, which is actually two methods wrapped
in a convenience script. I found it very handy for both building images locally during
development and running the build pipeline in a CI environment using the same Dockerfile.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
