<?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 storck.io</title>
    <link>https://storck.io/tags/docker/</link>
    <description>Recent content in Docker on storck.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2020 14:48:08 +0200</lastBuildDate>
    <atom:link href="https://storck.io/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a small Docker image to deploy your Go application</title>
      <link>https://storck.io/posts/minimal-dockerfile-for-golang-deployment/</link>
      <pubDate>Mon, 15 Jun 2020 11:38:00 +0200</pubDate>
      <guid>https://storck.io/posts/minimal-dockerfile-for-golang-deployment/</guid>
      <description>Docker image size matters. Here&amp;rsquo;s how you build a small image on top of debian:slim and why&#xA;that&amp;rsquo;s a better option than alpine or scratch.</description>
    </item>
    <item>
      <title>Add jemalloc to your Ruby Docker images, now!</title>
      <link>https://storck.io/posts/psa-switch-ruby-docker-to-jemalloc-now/</link>
      <pubDate>Fri, 08 May 2020 10:30:00 +0200</pubDate>
      <guid>https://storck.io/posts/psa-switch-ruby-docker-to-jemalloc-now/</guid>
      <description>&lt;p&gt;The topic of this post is neither new nor original, so I’m going to keep things short. People have been using jemalloc with MRI Ruby for years and praising it’s benefits all the while. The TL;DR here is: for Rails apps, using jemalloc will reduce memory consumption and might increase performance a little.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why&#34;&gt;Why?&lt;/h2&gt;&#xA;&lt;p&gt;To illustrate my own experience, here’s a Grafana graph showing the effect of switching to jemalloc on a production server running a few instances of a Rails application:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
