docker容器运行mysql持久化_OS x下使用Docker 持久化Mysql 数据出现问题
初学Docker ，请见谅。
系统: OS X 10.11.1 (15B42)
运行docker工具：Docker Quickstart Terminal virtualbox 5.0.8
docker 版本：Docker version 1.8.2, build 0a8c2e3镜像 docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
ubuntu14 v1 5044888e9250 6 days ago 254.8 MB
mysql 5.6 80013edd4cba 2 weeks ago 324.2 MB
dev/mysql latest 80013edd4cba 2 weeks ago 324.2 MB
基于dev/mysql镜像启动容器命令
docker run -p 3306:3306 -v ~/Develop/docker/php/mysql/data:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=123456 -it dev/mysql
错误
Initializing database
2015-11-10 03:19:14 0 /usr/sbin/mysqld (mysqld 5.6.27) starting as process 17 ...
2015-11-10 03:19:14 17 InnoDB: Using atomics to ref count buffer pool pages
2015-11-10 03:19:14 17 InnoDB: The InnoDB memory heap is disabled
2015-11-10 03:19:14 17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-11-10 03:19:14 17 InnoDB: Memory barrier is not used
2015-11-10 03:19:14 17 InnoDB: Compressed tables use zlib 1.2.8
2015-11-10 03:19:14 17 InnoDB: Using Linux native AIO
2015-11-10 03:19:14 17 InnoDB: Using CPU crc32 instructions
2015-11-10 03:19:14 17 InnoDB: Initializing buffer pool, size = 128.0M
2015-11-10 03:19:14 17 InnoDB: Completed initialization of buffer pool
2015-11-10 03:19:14 17 InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-11-10 03:19:14 17 InnoDB: Setting file ./ibdata1 size to 12 MB
2015-11-10 03:19:14 17 InnoDB: Database physically writes the file full: wait...
2015-11-10 03:19:14 17 InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2015-11-10 03:19:14 17 InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2015-11-10 03:19:15 7fa012ebc740 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2015-11-10 03:19:15 7fa012ebc740 InnoDB: Assertion failure in thread 140325488936768 in file fil0fil.cc line 875
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:19:15 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)
/usr/sbin/mysqld(handle_fatal_signal+0x481)
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8f0)
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x865)
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
/usr/sbin/mysqld
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
按照官网说明改为完整路径名
之后不会直接抛出错误 但是执行docker ps后没有出现容器的进程
总结
以上是生活随笔为你收集整理的docker容器运行mysql持久化_OS x下使用Docker 持久化Mysql 数据出现问题的全部内容，希望文章能够帮你解决所遇到的问题。
- 上一篇： 地狱之门东线操作快捷键(地狱之门按键)
- 下一篇： mysql 表数据diff,mysqld