Describe the bug
The python stack (0.2.3) already ensures the application does not run as root (the Docker creates a user called "worker" for this). A recent change also set the env variable APPSODY_USER_RUN_AS_LOCAL, which causes the docker file to be run as the local user...but this clashes with the UID of worker.
To Reproduce
Steps to reproduce the behavior:
Create a new project, initing with the python-stack
appsody run
...you will notice a line that says "/bin/sh: 1: pipenv: Permission denied" in the output, which means that piping failed to run and pull in any new dependencies defined by the local app. This failure is due to the mismatched UIDs
Describe the bug The python stack (0.2.3) already ensures the application does not run as root (the Docker creates a user called "worker" for this). A recent change also set the env variable APPSODY_USER_RUN_AS_LOCAL, which causes the docker file to be run as the local user...but this clashes with the UID of worker.
To Reproduce Steps to reproduce the behavior: