<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Harbor on Bill Glover</title>
		<link>https://old.bill.dev/tags/harbor/</link>
		<description>Recent content in Harbor on Bill Glover</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
			<managingEditor>hello@bill.dev (Bill)</managingEditor>
		
		
			<webMaster>hello@bill.dev (Bill)</webMaster>
		
		
		
			<lastBuildDate>Sun, 22 Sep 2024 19:05:36 +0100</lastBuildDate>
		
			<atom:link href="https://old.bill.dev/tags/harbor/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Docker and LetsEncrypt</title>
				<link>https://old.bill.dev/notes/docker-and-letsencrypt/</link>
				<pubDate>Thu, 20 Oct 2022 20:14:45 +0100</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/notes/docker-and-letsencrypt/</guid>
				<description>&lt;p&gt;If you are running a private container registry and using a certificate provided by &lt;a href=&#34;https://letsencrypt.org/&#34;&gt;LetsEncrypt&lt;/a&gt;, make sure you are using &lt;code&gt;fullchain.pem&lt;/code&gt; and not &lt;code&gt;cert.pem&lt;/code&gt;. If you miss this, the Docker CLI will report that your certificate is signed by an unknown authority.&lt;/p&gt;&#xA;&lt;p&gt;I have an instance of &lt;a href=&#34;https://goharbor.io/&#34;&gt;Harbor&lt;/a&gt; running as a private container registry. The certificate used by this instance is provided by LetsEncrypt and yet the Docker CLI refused to let me log in.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
