mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 16:49:47 +03:00
Cant use Azure Storage Fileshare #5135
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 @pelmeniking on GitHub (Jan 20, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I have deployed Bookstack in Azure as a Container. I added a Azure Storage Account and mapped the Storage to the container.
When the container is deployed it says " StdErr = mount error(13): Permission denied\nRefer to the mount.cifs(8)"
I checked the permissions on the Storage side wich seems ok.
Connecting to that share is also possible.
Do I need to paste some info into the Enviroment?
Can someone help?
Exact BookStack Version
24.10.03
Log Content
No response
Hosting Environment
Container deployed in Azure as a Container App using Azure Database for MSQL Server as database.
Application works but content cant be saved.
@ssddanbrown commented on GitHub (Jan 20, 2025):
I have no idea tbh as this will be quite specific to how Azure storage works with Linux containers in this context, and I have no experience of that.
The idea of remote mounting (what I assume is) SMB storage to linux-based containers sounds quite prone to problems.
@pelmeniking commented on GitHub (Jan 20, 2025):
Are there any restrictions to SMB protocol?
@ssddanbrown commented on GitHub (Jan 20, 2025):
At what level?
BookStack just expects a filesystem, and does sometimes set permissions.
Although basic, these things can start to throw edge-cases and issues when going through more complexity and abstractions. A windows share being mounted over a network to a local system, passed through into a container, is adding some extra layers of complexity for edge-cases to pop up.
Again though, I have no idea what Azure is doing in your context so not something I can really debug or provide detail of.
@pelmeniking commented on GitHub (Jan 20, 2025):
allright thanks