<?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>Docker on CX's Blog</title><link>https://blog.imcaoxuan.cn/en/tags/docker/</link><description>Recent content in Docker on CX's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>imcaoxuan.cn</copyright><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.imcaoxuan.cn/en/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker 信任自签名 CA 证书</title><link>https://blog.imcaoxuan.cn/en/posts/2026-10-23-docker-trust-custom-ca/</link><pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.imcaoxuan.cn/en/posts/2026-10-23-docker-trust-custom-ca/</guid><description>&lt;p&gt;When Docker uses HTTPS certificates issued by a private CA (such as step-ca), it is important to distinguish between &lt;strong&gt;Docker Engine pulling images&lt;/strong&gt; and &lt;strong&gt;an application inside a container accessing HTTPS&lt;/strong&gt;. Their certificate trust stores may not be the same.&lt;/p&gt;
&lt;h2 id="i-docker-engine-trusting-a-private-ca"&gt;I. Docker Engine Trusting a Private CA&lt;/h2&gt;
&lt;p&gt;This applies to &lt;code&gt;docker login&lt;/code&gt;, &lt;code&gt;docker pull&lt;/code&gt;, and &lt;code&gt;docker push&lt;/code&gt; when accessing a private image registry.&lt;/p&gt;
&lt;h3 id="trust-only-the-specified-registry-recommended"&gt;Trust Only the Specified Registry (Recommended)&lt;/h3&gt;
&lt;p&gt;Assume the registry address is &lt;code&gt;registry.example.com:5000&lt;/code&gt;:&lt;/p&gt;</description></item></channel></rss>