mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-16 19:06:45 +03:00
Image upload not working on Amazon ECS but works fine on localhost (docker container) #2349
Closed
opened 2026-02-05 03:45:24 +03:00 by OVERLORD
·
8 comments
No Branch/Tag Specified
development
l10n_development
release
v25-12
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#2349
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @HeavenlyEntity on GitHub (Aug 6, 2021).
Expected
I expect the image upload to work when changing the workspace logo also user profile images.
Actual Behavior
I am using
docker composeto spin up the container with the following storage ENVs:This instance works perfectly on my own machine but when I go to upload an image on the deployed container I get:

I made sure to include
RUN chown www-data:www-data -R /var/www/bookstack/bootstrap/cache /var/www/bookstack/public/uploads /var/www/bookstack/storage && chmod -R 755 /var/www/bookstack/bootstrap/cache /var/www/bookstack/public/uploads /var/www/bookstack/storagein my Dockerfile in case it was a permissions thing on the host. Yet still, this is working on my own machine. Can anyone help figure out what the underlying issue is? Using the solidnerd docker image.
Host Details:
Using AWS ECS cluster following the
docker context use ...&docker compose upto automate all the deployment processes and pre-reqs.@ssddanbrown commented on GitHub (Aug 8, 2021):
Hi @HeavenlyEntity,
What operating system are you using on AWS? And does this occur if you don't pass/set the volumes to the host?
Just wondering if something like selinux is at play here.
@HeavenlyEntity commented on GitHub (Aug 9, 2021):
Not sure tbh but looking at my Dockerfile I see:
Looks to be using Linux of some kind tho. There isn't any way for me to find out on AWS ECS, it shows the containers running as a service. There is no EC2 instance nor sign of one. But I do know the launch type is FARGATE.
Volumes are being made here for uploads and public for file uploads. Was told if there wasn't any upload volumes, creating books and shelves won't work as well.
@ssddanbrown commented on GitHub (Aug 12, 2021):
Thanks for the confirmation @HeavenlyEntity. To be honest I had EC2 and ECS mixed up. I have no idea how ECS works, From searching the storage side of things looks pretty complex. Are you doing something specific on the AWS side to supply/mount the storage/volume?
@HeavenlyEntity commented on GitHub (Aug 13, 2021):
No I just followed the instructions on your docs. But if you look at the
Dockerfile it shows the setting of the volumes but in my docker compose
file its the same as the default set up on the *solidnerd *repo only things
that were added were the environment variables.
On Thu, Aug 12, 2021, 1:06 PM Dan Brown @.***> wrote:
@ssddanbrown commented on GitHub (Aug 13, 2021):
Sure, the dockerfile defines some volumes but where/how do they map to outside of the container? From a quick search is that where efs comes in to play? https://docs.aws.amazon.com/AmazonECS/latest/developerguide/efs-volumes.html
Again though, I have no idea about this part of AWS, always find these kind of hosted services to be more trouble than they're worth for the kind of things I run.
@ssddanbrown commented on GitHub (Sep 29, 2021):
Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.
@HeavenlyEntity commented on GitHub (Oct 8, 2021):
Yes it still needs to be fixed. Nobody has commented on it because they
don't know or don't understand what is happening.
On Wed, Sep 29, 2021 at 12:54 PM Dan Brown @.***> wrote:
@ssddanbrown commented on GitHub (Oct 8, 2021):
@HeavenlyEntity If you're able to advise what i required to be changed in BookStack to fix your specific problem then feel free to open a new issue, referencing this one, with detail regarding the solution and problem it solves.
From my point of view this very much appears to be an issue related to hosting. We can only provide so much support when it comes to more complex hosting arrangements such as ECS. There has been no follow up attempts at providing details of if/how volumes are mapped outside the container which is the only obvious avenue I could see to resolve this.