Closed trevordavidlawrence closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I suspect this is due to using WSL2, there known problems with this as you can see here: https://github.com/linuxserver/docker-bookstack/issues/125
I suspect this is due to using WSL2, there known problems with this as you can see here: #125
That's what I had thought for a while, but I've also been able to reproduce this on a non-WSL Ubuntu VM. There, as before, if I pre-create that file (www/laravel.log
) in a bind mount the error does not occur.
I'm encountering this error as well on a GCS Debian instance with a fresh Bookstack install:
bookstack | chown: cannot dereference '/app/www/storage/logs/laravel.log': No such file or directory
bookstack | **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****
bookstack | **** The app may not work properly and we will not provide support for it. ****
So I don't think it's limited to WSL.
Same here on Debian 11.11 (OMV):
chown: cannot dereference '/app/www/storage/logs/laravel.log': No such file or directory
**** Permissions could not be set. This is probably because your volume mounts are remote or read-only. ****
**** The app may not work properly and we will not provide support for it. ****
EDIT:
Got around the issue by manually creating the laravel.log
file:
cd /your/bind/bookstack/volume/www
touch laravel.log # this must be run with the user running the container as per the "PUID/GUID" options of LSIO
Then restart the container and your OK to go.
This is usually caused by issues with the filesystem backing the docker container layers; are you running anything like ZFS/btrfs/mergerfs/etc?
This is usually caused by issues with the filesystem backing the docker container layers; are you running anything like ZFS/btrfs/mergerfs/etc?
mergerfs yes (only the data volumes, Docker engine is on a basic ext4). Do you know how to solve this permanently?
If it's just your mounted volumes it shouldn't be causing a problem with init, it's only if the docker filesystem (typically /var/lib/docker) is on a different filesystem.
I can replicate this on a clean install, so I expect it's an upstream change (probably a Laravel bump) that's caused it. I'll have a look this afternoon.
Can people test lspipepr/bookstack:v23.10.4-pkg-14e04100-dev-78d685a31f47de8708c037d76c89e4cf7856c734-pr-196
and see if it resolves their issues please.
Can people test
lspipepr/bookstack:v23.10.4-pkg-14e04100-dev-78d685a31f47de8708c037d76c89e4cf7856c734-pr-196
and see if it resolves their issues please.
I had the same issue yesterday. I can confirm that this image works as intended.
Is there an existing issue for this?
Current Behavior
At startup, an error is shown in the container logs:
And no logs from Laravel seem to be recorded.
Expected Behavior
No errors at container startup and Laravel log data is persisted.
Steps To Reproduce
docker compose logs bookstack
If I use a bind mount instead and put an empty file at
www/laravel.log
within the mounted directory, then the error goes away.I suspect the code that is
chown
-ing files symlinked into the/config
directory is choking on the fact thatlaravel.log
does not yet exist there.Environment
CPU architecture
x86-64
Docker creation
Container logs