Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

修改docker-compose.yml文件里的数据库密码后启动,结果MySQL的密码还是adminadmin #8

Open
iicey opened this issue Jul 19, 2019 · 6 comments

Comments

@iicey
Copy link

iicey commented Jul 19, 2019

No description provided.

@liumapp
Copy link
Owner

liumapp commented Jul 19, 2019

重新调整了一下 docker-compose.yml 对于设置密码的配置格式,请再测试一遍

如果还有异常请留言,或者参考这篇:docker-library/mysql#557

@ReyRen
Copy link

ReyRen commented Jul 20, 2019

个人感觉应该不是格式的问题, 而是作者的仓库中已经创建好了mysql.user并且表项就是adminadmin的root密码

@ReyRen
Copy link

ReyRen commented Jul 20, 2019

@iicey 解决方案:

  1. 将已经启动的mysql的mysql.user中将root密码改掉. 我之前尝试这种方法,但是有些问题(有待于进一步探讨)
  2. [推荐] docker-compose down后,直接将mysql删掉,重新up容器然后手动建solo的表
    这两种都请参考 issues7

@ghost
Copy link

ghost commented Jan 5, 2020

如果有volume的话,删除你的volume。注意删除volume会丢失数据。
原因是因为volume的一些设置只和第一次创建的时候有关。后面即使修改了docker-compose.yml里面的配置,也不会对volume里面的设置生效了。否则怎么能安全保护数据呢。

@PeterlitsZo
Copy link

重新调整了一下 docker-compose.yml 对于设置密码的配置格式,请再测试一遍

如果还有异常请留言,或者参考这篇:docker-library/mysql#557

你好,既然已经在表中预先就设置了 root 的密码,那就应该在 README 中提醒一下不要改比较好。

当然最好的办法就是。。。真的可以设置密码。

@alexallen1
Copy link

直接启动docker compose yaml 提示这个
please make sure database existed and database configuration [jdbc.*] in local.props is correct [msg=Unknown database 'solo'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants