<?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 OpenChain KWG</title><link>https://korea-wg.openchainproject.org/en/tags/docker/</link><description>Recent content in Docker on OpenChain KWG</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 10 Aug 2026 11:20:08 +0900</lastBuildDate><atom:link href="https://korea-wg.openchainproject.org/en/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Distribution of Dockerfiles: Who Is Responsible for Compliance?</title><link>https://korea-wg.openchainproject.org/en/blog/2021/05/04/dockerfiles/</link><pubDate>Tue, 04 May 2021 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/blog/2021/05/04/dockerfiles/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;Hello!&lt;/p&gt;&#10;&lt;p&gt;In April 2021, Till Jaeger, a well-known German open source lawyer, &lt;a href="https://jolts.world/index.php/jolts/article/view/147"&gt;published&lt;/a&gt; an article on who is responsible for the license compliance of the open source software included in the Docker image generated from a Dockerfile. Based on German law and the case law of the Court of Justice of the European Union (CJEU), Till explains that the Dockerfile provider must comply with license obligations.&lt;/p&gt;&#10;&lt;p&gt;This is a Korean translation of Till&amp;rsquo;s original English text. I added images to aid understanding, and here and there I added my own personal comments as blockquotes (in the polite register).&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;If you find translation errors or have questions, please contact me by email at &lt;a href="mailto:haksung@sk.com"&gt;haksung@sk.com&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;I am deeply grateful to &lt;a href="https://www.linkedin.com/in/%EC%98%81%ED%99%98-%EA%B9%80-4069b5135/"&gt;Sean&lt;/a&gt; of Kakao for his help reviewing this translation. ^^&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>