title: MySQL on Docker?
body: <p>I'm new to Docker and still exploring, I have this issue which may look silly but i'm really stuck.</p>
  <p>So I have a Spring boot app that uses a MySQL server and I want to run my app on a container.</p>
  <p>I managed to do &quot;run an app without MySQL&quot;.
  Now i'm following this tutorial in order to install MySQL in a container and use that container to run my app.</p>
  <p><a href="https://medium.com/@itsromiljain/dockerize-rest-spring-boot-application-with-hibernate-having-database-as-mysql-579abcc4edc4" rel="nofollow noreferrer">https://medium.com/@itsromiljain/dockerize-rest-spring-boot-application-with-hibernate-having-database-as-mysql-579abcc4edc4</a></p>
  <p>so when i run this command:</p>
  <pre><code> docker run -p 6603:3306 --name=docker-mysql --env=&quot;MYSQL_ROOT_PASSWORD=root&quot; --env=&quot;MYSQL_PASSWORD=root&quot; --env=&quot;MYSQL_DATABASE=test&quot; mysql
  </code></pre>
  <p>i get this error :
  <a href="https://i.stack.imgur.com/2ntHp.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/2ntHp.png" alt="enter image description here" /></a></p>
  <p>My guess is because I have MySQL installed and running in my machine, but I'm not convinced because the container is supposed to be isolated.</p>
  <p>PS: I'm running docker on a Windows 10 machine using windows containers.
  thank you.
  EDIT: this is the text format of the ERROR</p>
  <blockquote>
  <p>2019-02-08T09:09:23.467525Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 95
  2019-02-08T09:09:23.468063Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 95 in a file operation.
  2019-02-08T09:09:23.468133Z 1 [ERROR] [MY-012596] [InnoDB] Error number 95 means 'Operation not supported'
  2019-02-08T09:09:23.468193Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1'
  2019-02-08T09:09:23.468275Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
  2019-02-08T09:09:23.468387Z 1 [ERROR] [MY-012929] [InnoDB] InnoDB Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
  2019-02-08T09:09:24.070144Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
  2019-02-08T09:09:24.070172Z 0 [ERROR] [MY-013236] [Server] Newly created data directory /var/lib/mysql/ is unusable. You can safely remove it.
  2019-02-08T09:09:24.070759Z 0 [ERROR] [MY-010119] [Server] Aborting
  2019-02-08T09:09:24.072260Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.15)  MySQL Community Server - GPL.</p>
  </blockquote>