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

GID for the mysql group is not fixed #69

Open
inercia opened this issue Jul 11, 2017 · 2 comments
Open

GID for the mysql group is not fixed #69

inercia opened this issue Jul 11, 2017 · 2 comments

Comments

@inercia
Copy link

inercia commented Jul 11, 2017

While using MariaDB (in particular mariadb-10.0.30-28.1.x86_64) in CaaSP we have found a problem with the mysql group created at the spec file.

We are running MariaDB in a container that mounts persistent storage from the host. We need to use fixed UID and GID for the mysql user in the container, so that files created by mysql:mysql in the container appear with the same UID/GID in the host.

While the UID is hardcoded to be 60 it doesn't happen the same for the GID. We would like to know if it could be possible to create the mysql group with, for example, groupadd -r mysql -g 60 (or any other GID, as long as we could have a fixed GID).

@scarabeusiv
Copy link
Contributor

Well feel free to patch it with the -g ; but honestly no idea what group number it should use, probably the same as user?

@inercia
Copy link
Author

inercia commented Jul 12, 2017

I have submitted a PR, #70, where the GID is fixed to be 600... I think it is a reasonable safe group id, but we can change it if you don't think so...

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

2 participants