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

statx: Operation not permitted #339

Closed
ptm108 opened this issue Mar 22, 2022 · 3 comments
Closed

statx: Operation not permitted #339

ptm108 opened this issue Mar 22, 2022 · 3 comments
Labels
duplicate issue this issue is the same as one we already have open

Comments

@ptm108
Copy link

ptm108 commented Mar 22, 2022

Hi, facing an error w statx while trying to add SSL support to an existing neo4j project.

Container logs:

stat: cannot statx '/ssl': Operation not permitted

Folder /ssl is not accessible for user: 1003 or group 1003 or groups 1003, this is commonly a file permissions issue on the mounted folder.

Hints to solve the issue:
1) Make sure the folder exists before mounting it. Docker will create the folder using root permissions before starting the Neo4j container. The root permissions disallow Neo4j from writing to the mounted folder.
2) Pass the folder owner's user ID and group ID to docker run, so that docker runs as that user.
If the folder is owned by the current user, this can be done by adding this flag to your docker run command:
  --user=$(id -u):$(id -g)

I've tried all 3 hints but none has worked so far

Docker version: 18.03.1
Neo4j version: 4.4.4

@jennyowen
Copy link
Member

OK what are the file permissions on the folder you're mounting to /ssl?
What about the files inside that folder, are they also readable by the user you're running docker as?

@ptm108
Copy link
Author

ptm108 commented Mar 22, 2022

Thanks for the quick reply, I've tried running a chmod -R 777 on the ssl/ folder. Also changed the folder owner to the user. None of these worked for me

@jennyowen
Copy link
Member

This is a duplicate of #318. I'm going to close this issue and continue it over on #318.

@jennyowen jennyowen added the duplicate issue this issue is the same as one we already have open label Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate issue this issue is the same as one we already have open
Projects
None yet
Development

No branches or pull requests

2 participants