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

no directory logging in with home=/ on MySQL 5.7 x Docker containers #9

Closed
chusiang opened this issue Apr 18, 2018 · 2 comments
Closed

Comments

@chusiang
Copy link
Owner

chusiang commented Apr 18, 2018

I find the no directory logging in with home=/ bug with MySQL 5.7.

Solution for VM

  1. No Directory, Logging in with HOME=/ After MySQL 5.7 Upgrade
  2. mysql_solve.md

  1. Stop MYSQL service:

    $ sudo service mysql stop
    
  2. Change home directory of mysql from nonexistent to original directory where it is supposed to be

    $ sudo usermod -d /var/lib/mysql/ mysql
    
  3. Start MYSQL service

    $ sudo service mysql start
    
chusiang added a commit that referenced this issue Apr 18, 2018
I try to change the file permission of database and tables at
Docekrfile, but it is not working, so I change they at run time
with `run.sh`.

* `testlink:ubuntu-16.04`: Build pass, and login success.

         * Starting MySQL database server mysqld          [ OK ]

* `testlink:debian-8`: Build pass, and login success.

        [info] MySQL Community Server 5.6.39 is started.
@chusiang
Copy link
Owner Author

chusiang commented Apr 18, 2018

I try to manual fix it with change database file permission after the run playbook in Dockerfile, but it's not work.

So I choose change the file permission with run.sh at run time.

@chusiang
Copy link
Owner Author

為了解 MySQL 的這個 no directory logging in with home=/ 問題,又花掉 2 個多小時。開始把服務移植到 Docker 上後,才真的能體會到它與 VM (Vagrant) 的不同啊!

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

1 participant