Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App container is launched with wrong user ID #305

Closed
sveetch opened this issue Jul 19, 2018 · 0 comments
Closed

App container is launched with wrong user ID #305

sveetch opened this issue Jul 19, 2018 · 0 comments
Assignees
Labels

Comments

@sveetch
Copy link
Collaborator

sveetch commented Jul 19, 2018

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

  1. Launch richie app container with make run;
  2. Go to a page (logged as admin) where you can upload an image or any other file kind;
  3. Upload a file;
  4. You get a Permission denied error.

Environment

  • Richie version: 0.1.0 (1696320)
  • Platform: Ubuntu 18.04

Possible Solution
From @jmaupetit it seems related to our usage of docker-compose up -d in make run where we don't set an user.

@sveetch sveetch added the bug label Jul 19, 2018
jmaupetit added a commit that referenced this issue Jul 26, 2018
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
jmaupetit added a commit that referenced this issue Jul 26, 2018
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
jmaupetit added a commit that referenced this issue Jul 26, 2018
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants