fluse | A composable and type-safe fixture builder | Validation library

Whatever's serving your resources at the docker layer - gunicorn, uwsgi, whatever - will probably support serving static assets, and can do it significantly more efficiently than django itself.

In your situation, nginx is essentially external to your application. Instead of trying to "get your static assets into nginx", let the clients do that job and cache them in nginx once proxied. Nginx has good caching support.

If you really want to get the static assets into a , you can COPY --from=... like in a https://docs.docker.com/develop/develop-images/multistage-build/ to copy the static assets into your custom nginx container. Use the django container as the source - you'll have to make sure its built after your django container. This may not be possible completely within docker-compose. There's legitimate friction there; you'll have the same friction when/if you try to build and deploy docker artifacts to production servers.