<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.williams-net.org/index.php?action=history&amp;feed=atom&amp;title=Docker_and_Self-Signed_Certificates</id>
	<title>Docker and Self-Signed Certificates - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.williams-net.org/index.php?action=history&amp;feed=atom&amp;title=Docker_and_Self-Signed_Certificates"/>
	<link rel="alternate" type="text/html" href="https://wiki.williams-net.org/index.php?title=Docker_and_Self-Signed_Certificates&amp;action=history"/>
	<updated>2026-06-01T02:38:05Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.40.1</generator>
	<entry>
		<id>https://wiki.williams-net.org/index.php?title=Docker_and_Self-Signed_Certificates&amp;diff=181&amp;oldid=prev</id>
		<title>DrEdWilliams: Created page with &quot;While it is possible to tell docker to ignore the fact that a registry is using self-signed certificates, it is just as easy to put the certificates in a place on the client s...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.williams-net.org/index.php?title=Docker_and_Self-Signed_Certificates&amp;diff=181&amp;oldid=prev"/>
		<updated>2019-12-31T19:48:13Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;While it is possible to tell docker to ignore the fact that a registry is using self-signed certificates, it is just as easy to put the certificates in a place on the client s...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;While it is possible to tell docker to ignore the fact that a registry is using self-signed certificates, it is just as easy to put the certificates in a place on the client system where docker can use them to authenticate the server as it likes to do.  Assuming that the registry&amp;#039;s self-signed certificates were created as described [[Creating a Self-Signed Certificate|here]], you have the certificate in a files called &amp;#039;&amp;#039;cert.pem&amp;#039;&amp;#039; and the key in a file called &amp;#039;&amp;#039;key.pem&amp;#039;&amp;#039;.  The &amp;lt;hostname&amp;gt; used in the commands below must match &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXACTLY&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; the hostname provided when creating the keys.&lt;br /&gt;
&lt;br /&gt;
Docker allows local certificates to be placed in a directory on the client called &amp;#039;&amp;#039;/etc/docker/certs.d&amp;#039;&amp;#039;.  The contents of this directory are a set of subdirectories -- one for each system to be authenticated -- that contain the cert/key files for that system.  Using the certificate created above, issue these commands:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /etc/docker/certs.d/&amp;lt;hostname&amp;gt;&lt;br /&gt;
 sudo cp cert.pem /etc/docker/certs.d/&amp;lt;hostname&amp;gt;/domain.crt&lt;br /&gt;
 sudo cp cert.pem /etc/docker/certs.d/&amp;lt;hostname&amp;gt;/ca.crt&lt;br /&gt;
 sudo cp key.pem /etc/docker/certs.d/&amp;lt;hostname&amp;gt;/domain.key&lt;br /&gt;
&lt;br /&gt;
This must be done on any system that will be accessing the registry.  Alternatively, the entire &amp;lt;hostname&amp;gt; subdirectly can be copied to the other systems using scp:&lt;br /&gt;
&lt;br /&gt;
 sudo scp -r /etc/docker/certs.d/&amp;lt;hostname&amp;gt; &amp;lt;client-hostname&amp;gt;:/etc/docker/certs.d&lt;/div&gt;</summary>
		<author><name>DrEdWilliams</name></author>
	</entry>
</feed>