Percona container only runs the first time. #35
Comments
|
I am unable to reproduce it here (running all on Linux). Are you sure the directory was correctly filled with a real database or is this related to #36? $ docker run -d -e MYSQL_ROOT_PASSWORD=pass -e MYSQL_DATABASE=db \
-e MYSQL_USERNAME=user -e MYSQL_PASSWORD=pass \
-v "$PWD"/mysql:/var/lib/mysql --name db percona:5.7
10ebe77ca291ba5588d59fdb95aa304b27d03dc1c3ec347112c99172fff8ca1f
$ ls -l mysql/
total 176192
-rw-r----- 1 999 999 56 Dec 1 16:03 auto.cnf
-rw------- 1 999 999 1676 Dec 1 16:03 ca-key.pem
-rw-r--r-- 1 999 999 1083 Dec 1 16:03 ca.pem
-rw-r--r-- 1 999 999 1087 Dec 1 16:03 client-cert.pem
-rw------- 1 999 999 1680 Dec 1 16:03 client-key.pem
drwxr-s--- 2 999 999 4096 Dec 1 16:03 db
-rw-r----- 1 999 999 427 Dec 1 16:20 ib_buffer_pool
-rw-r----- 1 999 999 79691776 Dec 1 16:20 ibdata1
-rw-r----- 1 999 999 50331648 Dec 1 16:20 ib_logfile0
-rw-r----- 1 999 999 50331648 Dec 1 16:03 ib_logfile1
drwxr-s--- 2 999 999 4096 Dec 1 16:03 mysql
drwxr-s--- 2 999 999 4096 Dec 1 16:03 performance_schema
-rw------- 1 999 999 1680 Dec 1 16:03 private_key.pem
-rw-r--r-- 1 999 999 452 Dec 1 16:03 public_key.pem
-rw-r--r-- 1 999 999 1087 Dec 1 16:03 server-cert.pem
-rw------- 1 999 999 1676 Dec 1 16:03 server-key.pem
drwxr-s--- 2 999 999 12288 Dec 1 16:03 sys
$ docker stop db
db
$ docker rm db
db
$ docker run -v "$PWD"/mysql:/var/lib/mysql --name db percona:5.7
$ docker logs db
...
2016-12-02T00:33:53.339744Z 0 [Note] mysqld: ready for connections.
Version: '5.7.16-10' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release '10', Revision 'a0c7d0d' |
|
i have the exact same problem. |
|
@kersten I still cannot reproduce; any information you can give on your setup to help reproduce and debug? This time I tested on Windows 10 using Docker |
|
I have precisely this same problem on Windows 10 with Docker for Windows 10. I started things up yesterday and it worked great. Shut it down before going on to something else. Started it up again this afternoon. The DB server fails as shown below. Hope this helps. Thank you. |
|
I'm having the same problem. Any possible work around for this? |
|
In my environment, downgrading from Percona 5.7 to 5.6 solved the problem. |
|
I cannot reproduce this problem, either by starting a new container pointing to the existing directory, or by restarting a stopped container. However, I am on Ubuntu, not Windows. A) Is everyone on this thread running on Windows when they hit this problem? |
|
Here in our development team, there are a number of people running Docker on macOS. They do not have the problem. A couple of us are working on Windows; we have the problem. I just updated to 17.12 and still have the problem. Hope this helps. |
|
Perhaps this is really a duplicate of #42 and this #42 (comment) applies. |
|
Looking at the log excerpts posted here and in #42, it seems to me that this is a duplicate of #42. So in Percona 5.7, what does it need from the file system that it cannot get on a hosted volume? (Our docker configuration is shared across our entire dev team, so changing it to not use hosted volumes would be difficult.) |
|
wglambert
added
the
question
|
Issue seems to be a duplicate of #42 and that thread seems more active so I'm going to prune |
I'm on Windows 10, Docker 1.12.3 (8488) using the percona:latest image:tag.
I followed the strategy to keep the DB files on the host machine.
First time I run the container:
Awesome, up and running in a jiffy! Super excellent. IBDATA files got created in mysql_data directory as expected.
I work all day, go home and fire it up the next day, to see the container achieved Exited state only.
says
So, what should my
docker runcommand look like on runs 2-N ? Or am I missing something obvious? The documentation is so great, I'm surprised I'm having any issues. Particularly this part (under Environment Variables):The text was updated successfully, but these errors were encountered: