Need help deploying a django we application using docker containers

Question

Hi, I have a django web application. It was running on AWS EC2, I had some issues and i took a backup of the volume and I need to create a new instance and use the volume attached to the previous instance. I tried to do all the steps but I am getting error about the nginx. I am unsure how to fix it. I have the same configuration running on my local system. There are 3 services in my docker file and the webapp is not starting in ec2 when i run the docker-compose up. Can someone help me with this issue. I can share more information on the same.

version: '3.3'

services:
  db:
    image: mysql:latest
    hostname: 'db'
    ports:
      - 3307:3307
    restart: always
    container_name: mysql
    environment:
      MYSQL_DATABASE: 'adapt_db'
      MYSQL_ALLOW_EMPTY_PASSWORD: 'true'
    volumes:
      - ./dbdata:/var/lib/mysql
      - ./mysql-dump:/docker-entrypoint-initdb.d

backend:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: myapp
    command: bash -c "sleep 60 && python manage.py makemigrations && python manage.py migrate && python manage.py runserver 0.0.0.0:8000"
    ports:
      - 8000:8000
    volumes:
      - .:/home/myapp/
    depends_on:
      - db
    links:
      - db

nginx-proxy:
    depends_on:
      - backend
    image: nginx:alpine
    volumes: 
      - ./nginx.conf:/etc/nginx/conf.d/default.conf
    ports:
      - 80:80
      - 443:443

re:Post Agent · Answer

To deploy your Django web application using Docker containers on AWS EC2, you'll need to follow these steps and troubleshoot the nginx issue:

1. First, ensure that your EC2 instance has Docker and Docker Compose installed. You can install them using the appropriate package manager for your EC2 instance's operating system.

2. Attach the backup volume to your new EC2 instance and mount it to the correct directory where your application files are expected to be.

3. Make sure your Docker Compose file (docker-compose.yml) is in the correct directory on your EC2 instance.

4. Check your nginx configuration file (nginx.conf) to ensure it's correctly set up to proxy requests to your Django application. Make sure the upstream server points to the correct container name and port.

5. Verify that your Dockerfile is present and correctly configured to build your Django application.

6. Before running docker-compose up, try running docker-compose build to ensure all services are built correctly.

7. When running docker-compose up, use the -d flag to run in detached mode, and the --build flag to rebuild images if necessary: 
   docker-compose up -d --build

8. Check the logs of each container to identify any specific errors:
   docker-compose logs db
   docker-compose logs backend
   docker-compose logs nginx-proxy

9. For the nginx error, ensure that the nginx.conf file is correctly mapped in your docker-compose.yml and that the configuration is valid. You may need to adjust the nginx configuration to match your specific setup.

10. If the webapp is not starting, check the backend service logs for any Django-specific errors. Ensure that your database connection settings in Django's settings.py file are correct and match the db service configuration in your docker-compose.yml.

11. Make sure that the sleep command in your backend service gives enough time for the database to fully initialize before attempting to run migrations and start the Django server.

12. If you're still encountering issues, you may need to check if there are any port conflicts on your EC2 instance, or if the security group settings are correctly configured to allow traffic on the necessary ports (80, 443, 8000).

Remember to check your EC2 instance's security group to ensure it allows inbound traffic on the ports you're exposing (80, 443, 3307, 8000).

If you continue to face issues, you may need to provide more specific error messages from your logs to further diagnose the problem.
      
**Sources**  
[Deploying Containers on AWS: A Guide to ECS and EKS | AWS re:Post](https://repost.aws/articles/ARMYRTVoV1RKSs-0Zy1S2LgA/deploying-containers-on-aws-a-guide-to-ecs-and-eks)  
[Accelerate Migration and Modernization with a Reusable Solution to Deploy Container Applications on AWS | AWS Partner Network (APN) Blog](https://aws.amazon.com/blogs/apn/accelerate-migration-and-modernization-with-a-reusable-solution-to-deploy-container-applications-on-aws/)  
[QuickStart: Deploy a Docker application to Elastic Beanstalk - AWS Elastic Beanstalk](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/docker-quickstart.html)  
[Using the ECS-managed Docker platform branch in Elastic Beanstalk - AWS Elastic Beanstalk](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_ecs.html)

Riku_Kobayashi · Answer

Hello.

Is it possible for you to share the specific error message?  
There didn't seem to be any problems as far as I looked at docker-compose.yml.

Bhausab Paramanatti · Answer

Suggest that you modify your docker-compose.yml:

version: '3.3'

services:
  db:
    image: mysql:latest
    hostname: 'db'
    ports:
      - 3307:3307
    restart: always
    container_name: mysql
    environment:
      MYSQL_DATABASE: 'adapt_db'
      MYSQL_ALLOW_EMPTY_PASSWORD: 'true'
    volumes:
      - ./dbdata:/var/lib/mysql
      - ./mysql-dump:/docker-entrypoint-initdb.d

backend:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: myapp
    command: bash -c "
      ./wait-for-it.sh db:3307 --timeout=300 -- 
      python manage.py makemigrations && 
      python manage.py migrate && 
      python manage.py runserver 0.0.0.0:8000"
    ports:
      - 8000:8000
    volumes:
      - .:/home/myapp/
    depends_on:
      - db

nginx-proxy:
    image: nginx:alpine
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf
    ports:
      - 80:80
      - 443:443
    depends_on:
      - backend

networks:
  default:
    driver: bridge

This configuration:
Uses wait-for-it.sh to ensure the database is ready before starting the backend.
Adds a dependency for nginx-proxy on backend.
Explicitly defines a bridge network for all services.

If you're still encountering issues after trying these suggestions, please provide the specific error messages you're seeing from nginx or any other service. This will help in providing more targeted assistance.

Need help deploying a django we application using docker containers

Relevant content