<?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[RSS Feed]]></title><description><![CDATA[RSS Feed]]></description><link>http://direct.ecency.com</link><image><url>http://direct.ecency.com/logo512.png</url><title>RSS Feed</title><link>http://direct.ecency.com</link></image><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Apr 2026 17:48:32 GMT</lastBuildDate><atom:link href="http://direct.ecency.com/created/multi-stage/rss.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Reducing Docker image size with Multi-Stage builds]]></title><description><![CDATA[When to use Multi-Stage builds Some Dockerfile's have a lot of development inside. They need building tools, development libraries etc. The result is way to big image. An other good reason could be security.]]></description><link>http://direct.ecency.com/docker/@fieldworx/reducing-docker-image-size-with-multi-stage-builds</link><guid isPermaLink="true">http://direct.ecency.com/docker/@fieldworx/reducing-docker-image-size-with-multi-stage-builds</guid><category><![CDATA[docker]]></category><dc:creator><![CDATA[fieldworx]]></dc:creator><pubDate>Wed, 09 May 2018 20:57:15 GMT</pubDate></item></channel></rss>