<?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>Posts on CC's Sink</title><link>/posts/</link><description>Recent content in Posts on CC's Sink</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 14 Sep 2020 18:31:03 +0200</lastBuildDate><atom:link href="/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Jumping Ship: Migrating your container images from DockerHub to Quay.io</title><link>/posts/2020-jumping-ship-dockerhub-quay/</link><pubDate>Mon, 14 Sep 2020 18:31:03 +0200</pubDate><guid>/posts/2020-jumping-ship-dockerhub-quay/</guid><description>&lt;p&gt;Here are the steps I took to move my images from DockerHub to Quay. If you&amp;rsquo;re not interested in my thoughts or background, or know what you&amp;rsquo;re doing, scroll down to &amp;ldquo;Moving the Images&amp;rdquo;.&lt;/p&gt;
&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;I host several repositories at DockerHub, both for work and personally.
When DockerHub announced they would be &lt;a href="https://www.docker.com/pricing/resource-consumption-updates"&gt;deleting container images&lt;/a&gt; not used within 6 months, I understood.
They provide a great service to the community, and frankly I&amp;rsquo;m surprised this didn&amp;rsquo;t happen sooner. Docker Inc., and it&amp;rsquo;s (new-ish) owner Mirantis, don&amp;rsquo;t have the cash to burn like the Google and Amazon do.
Still though, it&amp;rsquo;s a bit sad, and can be frusterating. I believe DockerHub suffers from the same issue that &lt;a href="https://stackoverflow.com/q/13321556/1709894"&gt;GitHub / Git&lt;/a&gt; does. For people not in-the-know, they are synonyms. This is perpetuated by the fact that the default docker registry for everyone using the Docker container implementation, is docker.io.&lt;/p&gt;</description></item><item><title>Cloudflare with LetsEncrypt SSL Certificates + Apache's ProxyPass</title><link>/posts/2016-cloudflare-letsencrypt/</link><pubDate>Tue, 08 Nov 2016 14:53:00 +0000</pubDate><guid>/posts/2016-cloudflare-letsencrypt/</guid><description>&lt;p&gt;So, you want to use &lt;a href="https://letsencrypt.org/"&gt;LetsEncrypt&lt;/a&gt; to generate a free SSL certificate for your site behind Cloudflare and Apache (acting as a ReverseProxy). After many hours of research and tweaking, I got this setup to work. Here I will document my process for you to use. In the end, your setup will look something like this: &lt;em&gt;User &amp;lt;-(SSL)-&amp;gt; Cloudflare &amp;lt;-(SSL)-&amp;gt; Apache &amp;lt;&amp;ndash;&amp;gt; Your Webapp (not SSL)&lt;/em&gt;. This guide assumes you have a site already setup without SSL. I am using Ubuntu 16.04 for my setup, but the process should be similar for other OSes.&lt;/p&gt;</description></item></channel></rss>