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

'root' group is required #57

Open
hublol opened this issue Feb 18, 2018 · 4 comments
Open

'root' group is required #57

hublol opened this issue Feb 18, 2018 · 4 comments

Comments

@hublol
Copy link

hublol commented Feb 18, 2018

On systems where no group named 'root' exist, docker-volume-local-persist fails to start with the following error:
Starting... Found 0 volumes on startup
Group root not found

Is there a way to get around without having to add the root group?

@CWSpear
Copy link
Collaborator

CWSpear commented Apr 12, 2018

Not to my knowledge... I don't know if that group thing is required. I don't know much about this sort of thing... why isn't there a root group?

@geertbongers
Copy link

If I try to use the plugin in CoreOS I get the same error. There is a root group, but I think because docker or the socket is not owned by root:root but root:docker this error appears.

@CWSpear
Copy link
Collaborator

CWSpear commented Aug 22, 2018

I'm not sure I do anything explicitly to set the group to root, or otherwise require the group to be root. I feel like if anything, it should use the user and group of the owner of the local-persist process, which means it shouldn't try to set the group to root if it doesn't exist.

Are you seeing this error just running the binary directly? If so... I've got nothing. I just us Go's os.MkdirAll, which I'd assume uses the process's user/group by default. I'm not primarily a Go programmer, tho, so I may be wrong.

If you're running it through systemctl, you can add User= and Group= in your systemd.service for local-persist (located at /etc/systemd/system/docker-volume-local-persist.service by default) to something appropriate and see if that helps.

@kmpeterson
Copy link

I ran into this same issue trying to install on Clear Linux... no luck with updating the unit file, nor even changing group ownership of the socket itself. However, what seems to be the case is that whatever API is used is fed by the /etc/group file - for my distro, this file is optional and only has groups I've created. However, adding root:x:0: explicitly there was sufficient to start and use this plugin. Thanks!

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

4 participants