You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior/code
App container should be launched with user ID 1000 as configured with container FS permissions. This is required to create file like uploading image file in page contents.
Actual Behavior
Actually app container seems launched with user ID 10000 and so trying to upload a file lead to an error like [Errno 13] Permission denied: '/data/media/organizations/logo/6.jpg'.
Steps to Reproduce
Launch richie app container with make run;
Go to a page (logged as admin) where you can upload an image or any other file kind;
Richie's development image can now be built using a user ID passed as a
build argument. This allows us to run commands with this default user
when starting the docker-compose app service and prevent permission
issues with mounted volumes belonging to the local user.
Fix#305
Richie's development image can now be built using a user ID passed as a
build argument. This allows us to run commands with this default user
when starting the docker-compose app service and prevent permission
issues with mounted volumes belonging to the local user.
Fix#305
Richie's development image can now be built using a user ID passed as a
build argument. This allows us to run commands with this default user
when starting the docker-compose app service and prevent permission
issues with mounted volumes belonging to the local user.
Fix#305
Bug Report
Expected behavior/code
App container should be launched with user ID 1000 as configured with container FS permissions. This is required to create file like uploading image file in page contents.
Actual Behavior
Actually app container seems launched with user ID 10000 and so trying to upload a file lead to an error like
[Errno 13] Permission denied: '/data/media/organizations/logo/6.jpg'
.Steps to Reproduce
make run
;Permission denied
error.Environment
Possible Solution
From @jmaupetit it seems related to our usage of
docker-compose up -d
inmake run
where we don't set an user.The text was updated successfully, but these errors were encountered: