-
Notifications
You must be signed in to change notification settings - Fork 56
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
Error 507 NoWriteAccessOnLogsExceptions #180
Comments
Can you check that you have in your host: root@vps:Lychee-docker/lychee ✗
▶ ls -ll
total 24
drwxr-xr-x 2 root root 4.0K Jan 18 15:20 conf
drwxrwsr-x 2 guest guest 4.0K May 22 2023 logs
drwxr-xr-x 6 999 docker 4.0K Jan 18 15:19 mysql
drwxrwsr-x 2 guest guest 4.0K Jan 19 03:06 sym
drwxrwsr-x 14 guest guest 4.0K Dec 27 13:29 uploads i.e. make sure guest has write access on the |
External Permissions:
What GID/PID is necessary? So tired of this anti-root kick everyone is on, you can't run software the way you want anymore. Edit: Even chmodding (for the sake of testing) 777 and chowning to the lowest (highest number, lowest permission*) IDs doesn't help. Edit: Skipping permissions setting (because those cmds give whack permissions inside the container) and I can get through to |
That only matters if you're accessing the files from outside the container, or on a system that limits such things.
If you mean the ones in entrypoint, those set the recommended permissions inside the container.
If you want Laravel to work, you're going to have to (or manually hack all of your settings into Lychee's files I suppose) |
Nah, I had to set everything to 33 (www-data). A clean folder created by docker on first start of container and it'd not do the permissions correctly.
They break it (owner needed to stay 33 (www-data)). The built-in lychee is 1000 but www-data still couldn't read/write to it all.
I found out which .env it was talking about, container:/conf/.env. After setting PGID, PUID as I mentioned above (33) it all worked fine. Now my only trouble is that Lychee doesn't seem to comprehend Also, |
Ok, so.
The entrypoint script adds www-data (in the container) to the lychee group so that it has access.
This is a very unusual setup. You are free to use the Docker image as you wish, but if you do unusual things it's on you to figure out how to make them work, which you appear to have done. |
Not at all, this is a rather common setup sharing a unix socket instead of opening up ports and networking (and their overhead and latencies coupling keeping track of container names for DHCP etc) between containers and software. Nothing unusual about that at all.
The bit about Lychee not respecting APP_DIR (or in short, the inability to use a subpath on a reverse-proxy which is a proper setup) doesn't belong here, it was just off the top of my head. |
It does it at build time and again right here. This seems to work for every user who isn't you. |
I noticed the Dockerfile and the entrypoint.sh, that's where I discovered the means to skip those permissions setting. I even tested it without any volume mounts and it still behaved that way, so I'm wondering if it is this NAS (a Qnap). |
That's very possible. They sometimes do weird things to permissions. |
That is indeed why I mentioned it. It might also be why I need 33:33 on all of that. |
Hi,
I use the docker-compose.yml provided in the code.
I don't have any problem to start my docker but when i try to connect i have this error 507
NoWriteAccessOnLogsExceptions
Could not write in the logs. Check that storage/logs/ and containing files have proper permissions.
The text was updated successfully, but these errors were encountered: