<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="deploy-mysql-nonlinux-docker">
      </a>
      2.5.6.3 Deploying MySQL on Windows and Other Non-Linux Platforms with Docker
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045330078304">
  </a>
  <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Warning
   </div>
   <p>
    The MySQL Docker images provided by Oracle are built
          specifically for Linux platforms. Other platforms are not
          supported, and users running the MySQL Docker images from
          Oracle on them are doing so at their own risk. This section
          discusses some known issues for the images when used on
          non-Linux platforms.
   </p>
  </div>
  <p>
   Known Issues for using the MySQL Server Docker images from
        Oracle on Windows include:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      If you are bind-mounting on the container's MySQL data
            directory (see
      <a class="xref" href="docker-mysql-more-topics.html#docker-persisting-data-configuration" title="Persisting Data and Configuration Changes">
       Persisting Data and Configuration Changes
      </a>
      for
            details), you have to set the location of the server socket
            file with the
      <a class="link" href="server-system-variables.html#sysvar_socket">
       <code class="option">
        --socket
       </code>
      </a>
      option
            to somewhere outside of the MySQL data directory; otherwise,
            the server fails to start. This is because the way Docker
            for Windows handles file mounting does not allow a host file
            from being bind-mounted on the socket file.
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
