在Win10系统上使用docker部署GreateSQL报错
一、在Win10系统上使用docker部署GreateSQL报错，导致容器起不来，部署报错日志：2024-08-09 15:42:48 ERROR: mysqld failed while attempting to check config
2024-08-09 15:42:48 command was: "mysqld --verbose --help"
2024-08-09 15:42:48 2024-08-09T07:42:48Z UTC - mysqld got signal 8 ;
2024-08-09 15:42:48 Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
2024-08-09 15:42:48 BuildID=a1f65e4cb714f65d274e6079cb57f378fac77ac2
2024-08-09 15:42:48
2024-08-09 15:42:48 Build ID: a1f65e4cb714f65d274e6079cb57f378fac77ac2
2024-08-09 15:42:48 Server Version: 8.0.32-26 GreatSQL (GPL), Release 26, Revision a68b3034c3d
2024-08-09 15:42:48
2024-08-09 15:42:48 Thread pointer: 0x0
2024-08-09 15:42:48 Attempting backtrace. You can use the following information to find out
2024-08-09 15:42:48 where mysqld died. If you see no messages after this, something went
2024-08-09 15:42:48 terribly wrong...
2024-08-09 15:42:48 stack_bottom = 0 thread_stack 0x100000
2024-08-09 15:42:48 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e)
2024-08-09 15:42:48 /usr/sbin/mysqld(print_fatal_signal(int)+0x3af)
2024-08-09 15:42:48 /usr/sbin/mysqld(handle_fatal_signal+0xc5)
2024-08-09 15:42:48 /lib64/libpthread.so.0(+0x12d80)
2024-08-09 15:42:48 /usr/sbin/mysqld(sched_affinity::Sched_affinity_manager_numa::init(std::map<sched_affinity::Thread_type, char const*, std::less<sched_affinity::Thread_type>, std::allocator<std::pair<sched_affinity::Thread_type const, char const*> > > const&, bool)+0x3e)
2024-08-09 15:42:48 /usr/sbin/mysqld(sched_affinity::Sched_affinity_manager::create_instance(std::map<sched_affinity::Thread_type, char const*, std::less<sched_affinity::Thread_type>, std::allocator<std::pair<sched_affinity::Thread_type const, char const*> > > const&, bool)+0x54)
2024-08-09 15:42:48 /usr/sbin/mysqld(mysqld_main(int, char**)+0x25a4)
2024-08-09 15:42:48 /lib64/libc.so.6(__libc_start_main+0xe5)
2024-08-09 15:42:48 /usr/sbin/mysqld(_start+0x2e)
2024-08-09 15:42:48 Please help us make Percona Server better by reporting any
2024-08-09 15:42:48 bugs at https://bugs.percona.com/
2024-08-09 15:42:48
2024-08-09 15:42:48 You may download the Percona Server operations manual by visiting
2024-08-09 15:42:48 http://www.percona.com/software/percona-server/. You may find information
2024-08-09 15:42:48 in the manual which will help you identify the cause of the crash.
二、使用的镜像
registry.cn-beijing.aliyuncs.com/greatsql/greatsql:8.0.32-26
三、部署命令
docker run -d \
--name greatsql --hostname=greatsql \
-p 3308:3306 -p 33080:33080 -p 33062:33062 \
-e MYSQL_ROOT_PASSWORD='123' \
-lower_case_table_names=1 \
-e TZ=Asia/Shanghai \
greatsql/greatsql【这里换掉换成images的】
四、参考文献
https://mp.weixin.qq.com/s/lHnTVw7ldms3mqHphnPHpQ
看到第4行的日志，好像是遇到了BUG。 看起来像是遇到了docker兼容性的bug，一开始就报错了
2024-08-09 15:42:48 ERROR: mysqld failed while attempting to check config
...
2024-08-09 15:42:48 Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
可以试试在win10下跑个Linux虚拟机，再在Linux虚机中跑docker。
最好还是用原生的Linux环境来跑docker会更可靠。
页:
[1]