mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-11 03:13:15 +03:00
Upload image doesn't get uploaded for books or shelves #3825
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 @piraterx on GitHub (May 30, 2023).
Describe the Bug
I tried installing docker version of bookstack twice and both time, eventhough I upload cover image for shelves or book, it doesn't get uploaded. It happens with uploading image in chapter as well.
I am using this docker: https://github.com/linuxserver/docker-bookstack
I believe it is recommended version on your blog.
Steps to Reproduce
Go to any shelves or book, click upload image for cover, upload image you desire, and see if you can see that image in list of shelves or cover.
Expected Behaviour
There should be a cover image.
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
v23.05.2-ls81
PHP Version
No response
Hosting Environment
Debian 11
@ssddanbrown commented on GitHub (May 30, 2023):
Hi @piraterx,
docker-compose.ymlif you're using compose.@piraterx commented on GitHub (Jun 1, 2023):
Yes, Debain 11 instance is running for sure otherwise I wouldn't be able to access bookstack at all. Here is docker-compose.yml file:
@ssddanbrown commented on GitHub (Jun 1, 2023):
@piraterx Thanks for the compose file.
Sure, but can you specify how it's running? Are you running on bare-metal? A virtual machine? On Proxmox? LXC container? Online VPS service? What architecture (ARM or x86_64)?
@piraterx commented on GitHub (Jun 2, 2023):
Sorry, completely forgot to read How.. lol I am running is VM on proxmox.
@ssddanbrown commented on GitHub (Jun 2, 2023):
@piraterx Thanks.
@piraterx commented on GitHub (Jun 2, 2023):
It is sure VM on proxmox and I use ZFS storage for it in mirror vdev - separate for all VMs. .
@ssddanbrown commented on GitHub (Jun 2, 2023):
Okay, reason I ask is that I've seen very similar things recently for users running on docker on LXC on Proxmox on ZFS. The same setup on a different storage type did not have issues. See here for reference. Wondering if the same thing is at play for VMs.
@piraterx commented on GitHub (Jun 2, 2023):
But, I have another instance working on VM direct install created on ZFS but VM disk itself is LVM.
@ssddanbrown commented on GitHub (Jun 6, 2023):
Alright, I've just created a Debian 11.7 VM instance in proxmox, running a LSIO bookstack docker-compose setup using the default readme compose file, and book/shelf images worked fine.
The VM's disk is on ZFS proxmox storage, but the VM OS was installed with Ext4 for the root directory (Where containers exist).
Can you confirm the filesystem type used within the VM? For wherever the docker container and/or mounted volumes exist.
@piraterx commented on GitHub (Jun 6, 2023):
It is ext4. I can see image I uploaded under
ls bookstack/www/uploads/images/cover_bookshelf/but on website itself, no luck.
@ssddanbrown commented on GitHub (Jun 7, 2023):
Can you check your
bookstack/www/laravel.logfile, if existing, and confirm if lines are logged when uploading such an image. If so, can you share those logged lines?@piraterx commented on GitHub (Jun 10, 2023):
No such a file.
@AvrumFeldman commented on GitHub (Jun 14, 2023):
@piraterx since you are running on linuxserver/docker-bookstack the laravel.log is located in
/app/www/storage/logs/laravel.log@piraterx commented on GitHub (Jun 14, 2023):
Hey thanks, but I am not seeing this file anywhere in any folder. I went though each folders. this is what is if I do ls in there.
https://imgur.com/a/AeJkYL6
@ssddanbrown commented on GitHub (Jun 14, 2023):
If you run
ls -alh bookstack/www/uploads/images/cover_bookshelf/within your stack folder, what do the permissions look like?Does the uploaded image file have the same user/group set as the directory in which that file exists?
@piraterx commented on GitHub (Jun 16, 2023):
Hey so yes, whatever GUID and PUID is set in docker compose file, it has same permissions user/group for all folders and files.
I appreciate you looking into this.
@ssddanbrown commented on GitHub (Jun 16, 2023):
@piraterx Just to confirm, does that remain the case right after uploading an image? (Without restarting the container stack at all).
Just want to confirm that point because I think the container scripts set permissions on start-up, which may be affecting what's observed here.
@piraterx commented on GitHub (Jun 19, 2023):
Yes, I created new book and uploaded new cover image for that. User and group is same as what defined in docker-compose file.