Fixing Docker “Permission denied” for a Non-Root Container User

A Docker permission error is an ownership mismatch: a folder created by root (at image build or container startup) is being written to by an application that runs as a non-root user such as appuser, so Linux refuses the write. The fix is to change folder ownership with chown, not to loosen permissions with chmod 777.

Sometimes Docker does not fail loudly.

It does not say:

Hello Elena, your container is fine, but your app cannot write to the folder because the owner is wrong.

No. Docker prefers mystery.

You run the app. Everything looks healthy. The container is up. Nginx is serving. Flask is alive. Then suddenly uploads fail, backups do not appear, static files refuse to update, or Python throws one of those wonderfully unhelpful messages:

Permission denied

In my case, the fix was this command:

docker compose exec -u root web chown -R appuser:appuser /backups /app/protected_files /app/app/static

At first glance, it looks like a scary Linux spell.

But it is actually a very practical Docker permissions repair.

Let’s unpack it.

The Proper Fix: Own It at Build, Repair Volumes at Runtime

🔒 Subscribe to keep reading.