Skip to content
This repository has been archived by the owner on Feb 8, 2021. It is now read-only.

run mysql:5.7 failed #698

Open
xuchenhao001 opened this issue Jan 29, 2018 · 0 comments
Open

run mysql:5.7 failed #698

xuchenhao001 opened this issue Jan 29, 2018 · 0 comments

Comments

@xuchenhao001
Copy link

xuchenhao001 commented Jan 29, 2018

I want to run mysql:5.7 through hyperctl run --env MYSQL_ROOT_PASSWORD=root -d mysql:5.7, but get an error:

2018-01-29T04:44:50.700100Z 0 [ERROR] Can't start server : Bind on unix socket: No such device or address
2018-01-29T04:44:50.701281Z 0 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?
2018-01-29T04:44:50.702683Z 0 [ERROR] Aborting

When I get into container, I find there is a different between docker run & hyper run:

$ docker run -ti mysql:5.7 bash
$ cd /var/lib/
$ ls -lah
drwxr-xr-x  2 mysql mysql 4.0K Jan 29 04:52 mysql
drwxrwx---  2 mysql mysql 4.0K Jan 15 21:46 mysql-files
drwxr-x---  2 mysql mysql 4.0K Jan 15 21:46 mysql-keyring

$ hyperctl run -t mysql:5.7 bash
$ cd /var/lib/
$ ls -lah
drwxr-xr-x  2 root  root  4.0K Jan 29 04:56 mysql
drwxrwx---  2 mysql mysql 4.0K Jan 15 21:46 mysql-files
drwxr-x---  2 mysql mysql 4.0K Jan 15 21:46 mysql-keyring

Notice the owner of dir mysql is different, how to solve this problem? I have confirmed these two mysql:5.7 are the same officially supported.
Thanks!

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

No branches or pull requests

1 participant