title: Docker for Windows not using client certificates
body: <p>I'm having issue with connecting to private Docker registry.</p>
  
  <p>Setup:</p>
  
  <ul>
  <li><em>Windows10</em> (using HyperV)</li>
  <li><em>Docker for Windows version</em>: 18.03.0-ce</li>
  </ul>
  
  <p>Steps I did:</p>
  
  <ol>
  <li>Placed client certificates in C:/ProgramData/Docker/certs.d/&lt;private_registry_url&gt;/</li>
  <li>Placed client certificates in C:/Users//.docker/certs.d/&lt;private_registry_url&gt;/</li>
  <li>Root certificate imported in Windows "Trusted Root Certification Authorities" (otherwise I'm getting "X509: certificate signed by unknown authority")</li>
  </ol>
  
  <p>Result: Executing <code>docker login &lt;private_registry_url&gt;</code> and inserting correct credentials gives me: </p>
  
  <blockquote>
    <p>Error response from daemon: Get https&#58;//&lt;private_registry_url&gt;/v2/: remote error: tls: bad certificate</p>
  </blockquote>
  
  <p>which means that Docker is not sending correct client certificates. (When I execute <code>curl -client &lt;file.cert&gt; -key &lt;file.key&gt; https://&lt;private_registry_url&gt;/v2/</code> with client certificates I'm able to connect.</p>
  
  <p>When I connect to running HyperV machine there is missing <code>/etc/docker/certs.d/</code> folder. If I manually create <code>/etc/docker/certs.d/&lt;private_registry_url&gt;</code> and put my client certificates inside, everything starts to work! But after restarting Docker for Windows, folder <code>certs.d</code> in HyperV machine is missing and I'm not able to connect to private registry again.</p>
  
  <p>Any ideas what am I doing wrong?</p>