<p>The <a href="https://docs.docker.com/docker-for-windows/faqs/#are-symlinks-supported" rel="noreferrer">official Docker documentation</a> says:</p>

<blockquote>
  <p>Docker recognizes certs stored under <strong>Trust Root Certification
  Authorities</strong> or <strong>Intermediate Certification Authorities</strong>.</p>
</blockquote>

<p>That is, you can proceed <a href="https://github.com/moby/moby/issues/21189#issuecomment-288694477" rel="noreferrer">as the following</a>:</p>

<ul>
<li>Start > "Manage Computer Certificates" (also available in the control
panel) </li>
<li>Right-click on "Trusted Root Certification Authoritites" >
"All tasks" > "Import" </li>
<li>Browse to the crt file and then keep pressing "Next" to complete the wizard</li>
<li>Restart Docker for Windows</li>
</ul>

<p>In my case, the catch was that I imported the certificate via the context menu, and therefore it went to another folder where Docker could not access it. The certificate store behaves however very much like the normal Windows Explorer tree folder, so I had just to copy the certificate over to the supported category, and after Docker restart it worked.</p>

CC BY-SA 3.0
2017-12-19T09:59:42.513Z
I had 5 certificate files (.crt): root, server, server-chained, client, client-chained. First 3 is used in private docker-registry accessible via UI through SSL. Now which (out of 5) to be imported into windows ??
SACn
CC BY-SA 3.0
2017-07-11T15:03:09.683Z
2017-07-11T15:17:12.990Z
2017-07-11T15:17:12.990Z
Ta Mu
<p>Trying to use a customer registry from a Windows 10 system - a native Docker client in PowerShell.  </p>

<pre><code>PS &gt; docker --version

Docker version 17.06.0-ce, build 02c1287
PS &gt; docker pull REPO_URL/foo-bar:0.1

Error response from daemon: get https://REPO_URL/v2/: x509: 
certificate signed by unknown authority.
</code></pre>

<p>Importing the authority certificate to local user store via Windows tooling works for itself but has no effect here.</p>

CC BY-SA 3.0
2017-07-11T12:54:20.023Z
You may wish to follow the steps on this [Issue comment](https://github.com/moby/moby/issues/21189#issuecomment-288694477)
Tensibai
CC BY-SA 3.0
2017-07-11T13:39:21.527Z
works! now, shall I delete this question?
Ta Mu
CC BY-SA 3.0
2017-07-11T13:51:39.397Z
You may wish to self answer with the steps you did to make it work and maybe extend a little about how it differs on win10 than previous versions ?
Tensibai
CC BY-SA 3.0
2017-07-11T14:19:39.427Z
exactly those steps worked, with the only difference I did a right-click import and then had to copy over the certificate. Is that a valuable answer here?
Ta Mu
CC BY-SA 3.0
2017-07-11T14:22:01.290Z
I'd say yes, working with certificates is always a pain and it seems the official doc doesn't cover this point properly.
Tensibai
<docker><windows><powershell>
Configure Docker to use SSL for a private registry on Windows 10?
Ta Mu
# Configure Docker to use SSL for a private registry on Windows 10?

(Asked by: username_0 on 2017-07-10)

Trying to use a customer registry from a Windows 10 system - a native Docker client in PowerShell.  
PS > docker --version

Docker version 17.06.0-ce, build 02c1287
PS > docker pull REPO_URL/foo-bar:0.1

Error response from daemon: get https://REPO_URL/v2/: x509: 
certificate signed by unknown authority.

Importing the authority certificate to local user store via Windows tooling works for itself but has no effect here.

**Tags:** docker, windows, powershell

> **Comments:**
> **username_1**: You may wish to follow the steps on this [Issue comment](https://github.com/moby/moby/issues/21189#issuecomment-288694477)  
> **username_0**: works! now, shall I delete this question?  
> **username_1**: You may wish to self answer with the steps you did to make it work and maybe extend a little about how it differs on win10 than previous versions ?  
> **username_0**: exactly those steps worked, with the only difference I did a right-click import and then had to copy over the certificate. Is that a valuable answer here?  
> **username_1**: I'd say yes, working with certificates is always a pain and it seems the official doc doesn't cover this point properly.  

---

## 1 answers

### Answer by username_0 on 2017-07-11. Score: 10 | Accepted answer

The [official Docker documentation](https://docs.docker.com/docker-for-windows/faqs/#are-symlinks-supported) says:

> Docker recognizes certs stored under **Trust Root Certification
> Authorities** or **Intermediate Certification Authorities**.

That is, you can proceed [as the following](https://github.com/moby/moby/issues/21189#issuecomment-288694477):

* Start > "Manage Computer Certificates" (also available in the control
  panel)
* Right-click on "Trusted Root Certification Authoritites" >
  "All tasks" > "Import"
* Browse to the crt file and then keep pressing "Next" to complete the wizard
* Restart Docker for Windows

In my case, the catch was that I imported the certificate via the context menu, and therefore it went to another folder where Docker could not access it. The certificate store behaves however very much like the normal Windows Explorer tree folder, so I had just to copy the certificate over to the supported category, and after Docker restart it worked.

> **Comments:**
> **username_2**: I had 5 certificate files (.crt): root, server, server-chained, client, client-chained. First 3 is used in private docker-registry accessible via UI through SSL. Now which (out of 5) to be imported into windows ??  

---

