Those files and folders should belong to "django" user and the permissions on them should reflect the Dockerfile.
What actually happened?
The ownership and permissions on those files is set before the files are actually copied from the local project folder to the container file system, thus they apply to nothing. The order of instructions in the Dockerfile is wrong.
Impact
Low
Urgency
Now
What browsers are you seeing the problem on?
No response
What operating system are you using?
Linux
Relevant log output
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Adding a volume in docker-compose causes the ownership and permission of the files and folders in the app container to change. For this reason is better to have 2 docker-compose files:
docker-compose.yml for the ci/cd and to just run the project
docker-compose.dev.yml to use for development, since this needs a volume to test real-time changes in the code and to run tailwind commands, which can only be run as root user
What did you expect?
Those files and folders should belong to "django" user and the permissions on them should reflect the Dockerfile.
What actually happened?
The ownership and permissions on those files is set before the files are actually copied from the local project folder to the container file system, thus they apply to nothing. The order of instructions in the Dockerfile is wrong.
Impact
Low
Urgency
Now
What browsers are you seeing the problem on?
No response
What operating system are you using?
Linux
Relevant log output
No response
Code of Conduct