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
Fix(Installation): Adjust the data directory's permissions to 777 to allow access for users in the container. #8876
Fix(Installation): Adjust the data directory's permissions to 777 to allow access for users in the container. #8876
Conversation
…mple 'docker-compose-file' to specify the container execution user as 'root' to ensure the mounted volume can be accessed.
Waiting for approval from someone in the solo-io org to start testing. |
Thanks for the contribution @orange-guo! Can you share the steps in your PR body to outline how to reproduce this behavior and how to demonstrate that this works as expected? Can you also check out our recommendations for Pull Request guidelines (https://github.com/solo-io/gloo/blob/main/devel/contributing/pull-requests.md#include-a-changelog-entry), specifically the part about adding a changelog entry? |
/test |
/skip-changelog small script update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! One question about a way we might be able to limit the permissions further.
Whatever we introduce in this script, we'll likely need to add to https://github.com/solo-io/gloo/blob/main/install/docker-compose-consul/prepare-directories.sh as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Happy to approve once the change-log issues are resolved 👍🏼 |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 Thanks for the contribution @orange-guo!
How to reproduce this behavior
After executing the 'prepare-directories.sh' script as per the documentation to set up the 'data' directory and launching the containers using 'docker compose up,' an error was encountered in the Gloo container:
It seems that the issue revolves around the permissions required for the 'data' directory. The user inside the container needs read and write permissions for 'other' (xx7) to access files within 'data'.
Solution