Thanks a lot for your input, it helped me figure it out!
Antonis, you're right, it's basically not possible that those files are
owned by root when manage.py is run as "user". This gave me the clue that
those directories (and many of the staticfiles) were created at a time
before I switched to
I literally spent the last few days trying to fix this same issue (apart
from your "Django SECRET_KEY in a .env file" problem, which I don't
understand as it does not seem related).
There are numerous suggestions on Stack Overflow and various blogs; which
either don't work or are too complex to
Everything works fine except for the collectstatic command (in entrypoint.sh),
which creates the "staticfiles" directory but it's owned by root.
This is not possible. If "manage.py" is running as a non-root user, it wouldn't
be possible for it to create a directory owned by root. Something else i
On 14/02/2022 10:14 pm, 'Tim' via Django users wrote:
Hi all,
I'm deploying Django 4 via docker-compose. For security reasons, the
Dockerfile creates a non-root user before running the entrypoint.sh
script (which does migrations, collectstatic and starts the server
with gunicorn). All app file
Hi all,
I'm deploying Django 4 via docker-compose. For security reasons, the
Dockerfile creates a non-root user before running the entrypoint.sh script
(which does migrations, collectstatic and starts the server with gunicorn).
All app files are "chown"ed by this non-root user.
Everything works
5 matches
Mail list logo
