-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unable to access because of permission problems #8
Comments
@lightlike Can you reproduce this issue on the current version?
|
It is still happening with the current image when I set this up from scratch. (The storage I fixed manually works perfectly still) The compose file: version: '2'
services:
5etools:
container_name: 5etools-test
environment:
- SOURCE=GITHUB
#- OFFLINE_MODE=TRUE
- TZ=Europe/Berlin
ports:
- '8088:80/tcp'
volumes:
- '/srv/dev-disk-by-label-DATA0/DockerData/test:/usr/local/apache2/htdocs'
restart: unless-stopped
image: jafner/5etools-docker The permissions of drwxrws---+ 21 1000 1000 4096 6. Sep 08:08 . If you need anything else please let me know. |
Are you able to serve that directory with a vanilla If not, I would look further into the file/directory permissions as the culprit. If so, I'll take another look at how my script interacts with ownership and permissions. |
I get the same 403 Forbidden from a static nginx docker with the following config: version: '2'
services:
nginx:
image: nginx
container_name: nginx-test
ports:
- 8088:80
volumes:
- /path/to/5etools:/usr/share/nginx/html:ro I do not know if this would be overkill but the s6-overlay project tries to remedy those problems by accepting a UID and GID for the service to be run with. (and a lot of other usefull stuff) |
I get a permission error when trying to access the files from from the browser (HTTP 403)
This seems to be because the
httpd
service cannot access the files.Created Permissions:
rwxrwx---
Needed Permissions:
rwxrwxr-x
This should be fixed by either setting the
httpd
user toPUID
andPGID
or by executingchmod o+rx /usr/local/apache2/htdocs/*
.The text was updated successfully, but these errors were encountered: