<?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"><channel><title><![CDATA[Dockerfile with 2 x FROM sources]]></title><description><![CDATA[<p dir="auto">I've seen a few interesting FOSS apps which in their Dockerfiles have 2 <code>FROM ...</code> statements.<br />
e.g.</p>
<pre><code>FROM elixir:1.12-alpine as build
...
...
FROM elixir:1.12-alpine
...
...
</code></pre>
<p dir="auto">Ignoring that these examples are not the Cloudron base images, just wondering how this might be handled in building a Cloudron package.  Is it possible ?<br />
<em>Probably going will turn out to be a dumb question : humour the newbie</em></p>
]]></description><link>https://forum.cloudron.io/topic/6434/dockerfile-with-2-x-from-sources</link><generator>RSS for Node</generator><lastBuildDate>Mon, 20 Apr 2026 03:01:27 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/6434.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Feb 2022 17:31:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 22:33:00 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/fbartels" aria-label="Profile: fbartels">@<bdi>fbartels</bdi></a> thanks, nice example <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=16ee7d1409f" class="not-responsive emoji emoji-android emoji--+1" style="height:23px;width:auto;vertical-align:middle" title=":+1:" alt="👍" /></p>
]]></description><link>https://forum.cloudron.io/post/42850</link><guid isPermaLink="true">https://forum.cloudron.io/post/42850</guid><dc:creator><![CDATA[timconsidine]]></dc:creator><pubDate>Thu, 03 Feb 2022 22:33:00 GMT</pubDate></item><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 21:37:58 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/timconsidine" aria-label="Profile: timconsidine">@<bdi>timconsidine</bdi></a> Multi stage builds are super easy to use. As long as binaries are compatible, you could even pull binaries from pre existing containers.</p>
<p dir="auto">I’m doing the same in <a href="https://github.com/fbartels/cloudron-drone-app/blob/master/Dockerfile" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/fbartels/cloudron-drone-app/blob/master/Dockerfile</a></p>
]]></description><link>https://forum.cloudron.io/post/42848</link><guid isPermaLink="true">https://forum.cloudron.io/post/42848</guid><dc:creator><![CDATA[fbartels]]></dc:creator><pubDate>Thu, 03 Feb 2022 21:37:58 GMT</pubDate></item><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 21:20:07 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/girish" aria-label="Profile: girish">@<bdi>girish</bdi></a> thanks, will research and play around a bit</p>
]]></description><link>https://forum.cloudron.io/post/42845</link><guid isPermaLink="true">https://forum.cloudron.io/post/42845</guid><dc:creator><![CDATA[timconsidine]]></dc:creator><pubDate>Thu, 03 Feb 2022 21:20:07 GMT</pubDate></item><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 19:12:06 GMT]]></title><description><![CDATA[<p dir="auto">This style is called <a href="https://docs.docker.com/develop/develop-images/multistage-build/" target="_blank" rel="noopener noreferrer nofollow ugc">multistage builds</a>, if you want to search/read more. FWIW, they will work fine on Cloudron, we use standard docker images. That all our apps use <code>cloudron/base:3.2.0</code> as the base image is only a convention that helps us maintain things more easily. (as in, if each each app package had it's own coding style and convention, it becomes hard for us to navigate the code and update them).</p>
]]></description><link>https://forum.cloudron.io/post/42841</link><guid isPermaLink="true">https://forum.cloudron.io/post/42841</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 03 Feb 2022 19:12:06 GMT</pubDate></item><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 18:08:02 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mehdi" aria-label="Profile: mehdi">@<bdi>mehdi</bdi></a> thanks for the explanation <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=16ee7d1409f" class="not-responsive emoji emoji-android emoji--+1" style="height:23px;width:auto;vertical-align:middle" title=":+1:" alt="👍" /><br />
Maybe I will get brave and try it out on a project</p>
]]></description><link>https://forum.cloudron.io/post/42837</link><guid isPermaLink="true">https://forum.cloudron.io/post/42837</guid><dc:creator><![CDATA[timconsidine]]></dc:creator><pubDate>Thu, 03 Feb 2022 18:08:02 GMT</pubDate></item><item><title><![CDATA[Reply to Dockerfile with 2 x FROM sources on Thu, 03 Feb 2022 17:56:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/timconsidine" aria-label="Profile: timconsidine">@<bdi>timconsidine</bdi></a> This is just a Docker syntax that allow you to have a temporary container that does some stuff (usually building things), then you can access files built during previous steps in subsequent ones and add them to your image.</p>
<p dir="auto">Basically, it's just a way to simplify cleanup : instead of installing a bunch of tools that you only need during build time, then having to remove them (or worse, leave them in the final image), you can do the build in the temporary container, then import the build results in the final container.</p>
]]></description><link>https://forum.cloudron.io/post/42835</link><guid isPermaLink="true">https://forum.cloudron.io/post/42835</guid><dc:creator><![CDATA[mehdi]]></dc:creator><pubDate>Thu, 03 Feb 2022 17:56:24 GMT</pubDate></item></channel></rss>