mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 19:06:06 +03:00
bookstack after upg doesn't work #5136
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @balgerion on GitHub (Jan 21, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
Good morning,
Yesterday my bookstack updated (it have latest tag on it)
and i wake up with this: :)
there is no error in logs and i dont see any braking changes on github notes.
docker compose:
services:
bookstack:
image: linuxserver/bookstack:arm64v8-latest
deploy:
placement:
constraints:
- node.role == worker
environment:
- APP_DEBUG=true
- PUID=1001
- PGID=988
- DB_HOST=192.168.1.21
- DB_PORT=3306
- DB_DATABASE=bookstack
- DB_USERNAME=
- DB_PASSWORD=""
- APP_URL=https://wiki.balgeriada.com
- APP_KEY=
- CACHE_DRIVER=database
- SESSION_DRIVER=database
volumes:
- uploads:/var/www/bookstack/public/uploads
- storage:/var/www/bookstack/storage/uploads
ports:
- "8186:80"
volumes:
uploads:
driver_opts:
type: nfs
o: nfsvers=4.2,addr=192.168.1.21
device: ":/mnt/Balgeriada1/docker/app/bookstack/uploads"
storage:
driver_opts:
type: nfs
o: nfsvers=4.2,addr=192.168.1.21
device: ":/mnt/Balgeriada1/docker/app/bookstack/storage"
Exact BookStack Version
v24.12.1-ls189
Log Content
No response
Hosting Environment
Docker , docker swarm
@ssddanbrown commented on GitHub (Jan 21, 2025):
Hi @balgerion,
Those are not the expected/intended volume mounts for that container image.
Before anything, be super careful about any changes you make. There's a high potential of data loss.
Backup any storage volumes involved, and maybe the running container data too if existing and/or snapshot/backup the host machine.
The linuxserver image manages things so there's only a single
/configvolume mount-point to use/manage.Ideally you should switch over to following the expected convention for the image.
You may need to move existing data.
There's a location mapping in the readme of that container image: https://github.com/linuxserver/docker-bookstack?tab=readme-ov-file#bookstack-file--directory-paths
@balgerion commented on GitHub (Jan 21, 2025):
oohhh you are right but it was working for almost month without issue :). Changed to proper config and still have simillar error
Btw thank you for your help and time
files in correct place:
docker compose:
services:
bookstack:
image: linuxserver/bookstack:arm64v8-latest
deploy:
placement:
constraints:
- node.role == worker
environment:
- APP_DEBUG=true
- PUID=1001
- PGID=988
- DB_HOST=192.168.1.21
- DB_PORT=3306
- DB_DATABASE=bookstack
- DB_USERNAME=
- DB_PASSWORD=""
- APP_URL=https://wiki.balgeriada.com
- APP_KEY=
- CACHE_DRIVER=database
- SESSION_DRIVER=database
volumes:
- config:/config
ports:
- "8186:80"
volumes:
config:
driver_opts:
type: nfs
o: nfsvers=4.2,addr=192.168.1.21
device: ":/mnt/Balgeriada1/docker/app/bookstack/config"
@tfeldmann commented on GitHub (Jan 21, 2025):
Having the same problem here:
Found this in the container logs:
But using the newer .conf files didn't change anything.
Found no errors in nginx or bookstack logs. How can I debug this?
@ssddanbrown commented on GitHub (Jan 21, 2025):
I'll spin up a fresh stack myself to check it's not something baked into the image.
@tfeldmann Are you also running on ARM?
@ssddanbrown commented on GitHub (Jan 21, 2025):
A fresh stack on standard x86_64 seems to work okay.
Full compose
@ssddanbrown commented on GitHub (Jan 21, 2025):
@balgerion Are you running docker on Windows? If so, is the Windows host also ARM? Just getting thrown off by the Windows screenshot, but not sure if you're just viewing a remote mounted folder or something.
@balgerion commented on GitHub (Jan 21, 2025):
On Linux - dietpiOS on radxa zero3 - I have ten of them running docker swarm for many apps.
@tfeldmann commented on GitHub (Jan 21, 2025):
I noticed I‘m missing an APP_KEY. Will try this out.
@tfeldmann commented on GitHub (Jan 21, 2025):
Doesn't work. How would you debug this? The docker logs look fine :/
@ssddanbrown commented on GitHub (Jan 21, 2025):
@tfeldmann Yeah, the logs will look fine for this.
I think I've seen this before in issues with specific write access, but the paths I'm thinking of should be in-container.
Are you also running on ARM?
@ssddanbrown commented on GitHub (Jan 21, 2025):
I'd also be interested to know if everything works okay if you set the image & version to be
lscr.io/linuxserver/bookstack:v24.12.1-ls187. That's their build from last week.@ssddanbrown commented on GitHub (Jan 21, 2025):
Another report via Reddit, again ARM based: https://www.reddit.com/r/BookStack/comments/1i6jrb0/started_getting_this_error_in_bookstack_login_page/
@balgerion commented on GitHub (Jan 21, 2025):
Its working! almost shit my pants here :)
@jx24734 commented on GitHub (Jan 21, 2025):
I am also seeing this error on an ARM based machine and can confirm that moving to that build solved the issue for me as well.
@gauravpandey44 commented on GitHub (Jan 21, 2025):
Just now tested this tag is working fine for ARM64 :
lscr.io/linuxserver/bookstack:v24.12.1-ls187. That means something is wrong with latest onelinuxserver/bookstack:24.12.1.@ssddanbrown commented on GitHub (Jan 22, 2025):
Okay, I've been doing a lot of testing on ARM.
It seems that this is at the PHP level of things in the container rather than in at the BookStack level, since I tracked down the exact logic to create a simplistic test case:
This would then fail on the PHP CLI inside the container, but succeed in all other PHP environments I ran it in.
This reflected a fundamental issue in PHP tokenization for PHP in the container.
Despite the image project files reporting PHP 8.3.16 was in use, PHP 8.3.15 was reported within the container. That said, some packages do appear to be 8.3.16. I think these are ones installed specifically for the BookStack container upon base.
Either there's an issue in the alpine PHP 8.3.15 packages, or this was due to mixing PHP 8.3.15/8.3.16 packages within one installation (I suspect the latter) but I could not confirm this as I had trouble specifically installing PHP 8.3.15 alone within an alpine system.
Running
apk upgradewithin the container, and clearing cached view files, got things working again.I'll gather my findings and report them to the linuxserver project to make them aware this issue exists so they can maybe plan/implement a solution.
@ssddanbrown commented on GitHub (Jan 22, 2025):
Linuxserver team are now on it, fixed image now being built: https://github.com/linuxserver/docker-bookstack/issues/260#issuecomment-2605935774
@tfeldmann commented on GitHub (Jan 22, 2025):
It's working again 👍 Thanks for the quick support!
@ssddanbrown commented on GitHub (Jan 22, 2025):
No worries.
Thanks all for reporting/sharing details to help debug.
Since this has now been fixed elsewhere I'll go ahead and close this off.