First, sorry if this is intended behavior and not bug.
I've have created a new project with all default options, except for opting to use docker.
Everything works as the docs suggests, until I have to use a manage.py command that will create files, ex:
docker compose -f docker-compose.local.yml run --rm django python manage.py startapp test_app or even better, just manage startapp test_app
Files are created with root as the owner instead of my user. I'm aware of this old issue, but for now my wordaround is using -u dev-user to run manage commands.
Should this be mentioned in the docs or can you point me the correct approach?
First, sorry if this is intended behavior and not bug.
I've have created a new project with all default options, except for opting to use
docker.Everything works as the docs suggests, until I have to use a
manage.pycommand that will create files, ex:docker compose -f docker-compose.local.yml run --rm django python manage.py startapp test_appor even better,just manage startapp test_appFiles are created with
rootas the owner instead of my user. I'm aware of this old issue, but for now my wordaround is using-u dev-userto runmanagecommands.Should this be mentioned in the docs or can you point me the correct approach?