dockerizing-django | Blog post - & gt ; https : //realpython | Continuous Deployment library

I am trying to Dockerizing Django with Postgres, Gunicorn, and Nginx via the tutorial on

https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/

I am was getting an error while docker is in step 7 i.e,

Step 7/23 : RUN pip wheel --no-cache-dir --no-deps --wheel-dir /usr/src/app/wheels -r requirements.txt

I was able to update the Dockerfile.prod to conquer this error, but i am getting another error in step 21

Step 21/26 : RUN pip install --no-cache /wheels/*

This is my updated Dockerfile.prod

I am running Django with PostgreSQL in a docker-compose setup for development. Each time I restart the application container, the database is empty, even though I do neither restart the DBMS container nor do I drop the DBMS's data volume. It seems that Django is dropping all tables upon restart. Why?

My setup closely follows the description here. That is, my compose file looks as follows (simplified):

So I am following this tutorial and have gotten all the way to the 'media' section and when I run the command:

docker-compose exec web python manage.py startapp upload

it all works fine but when I open the newly created views.py file and edit and try to save I get a permission denied error. I can open the file as root and edit it but now thru my Atom code editor. I don't know where I am going wrong can someone help me? Here's my code:

Dockerfile:

I have dockerized a Django project with Postgres, Gunicorn, and Nginx following this tutorial.

Now i want to move the application to azure container instances. Can i simply create a container group following this tutorial, and expect the container images to communicate the right way?

To run the project locally i use docker-compose -f docker-**compose.prod.yml** up -d --build But how is the communication between the containers handled in azure container instances?

The docker-compose.prod.yml looks like this:

I have the following Nginx configuration for my Django application:

In many Docker tutorials based on Python (such as: this one) they use the option PYTHONDONTWRITEBYTECODE in order to make Python avoid to write .pyc files on the import of source modules (This is equivalent to specifying the -B option).

What are the risks and advantages of setting this option up?

Following This Tutorial

Basically my issue is that when I try to run a certain command, I get a permission error. This ends up affecting other parts of my workflow despite not having an immediate impact.

When Running: