Docker新手求助：Gunicorn+Nginx+Django容器更新后502错误解决

Hey there! Let's walk through what's causing your 502 error and get your app back up and running the right way—no full rebuild required.

First, Why the 502? #

Your new web container isn't connected to the service_network that your Nginx proxy and PostgreSQL database are using. Without this network, Nginx can't reach your web service, hence the 502 Bad Gateway error.

Quick Fix: Connect Your Existing Container to the Network #

If your new djangotango-web container is already running, you can immediately connect it to the correct network with this command:

sudo docker network connect service_network djangotango-web

This should resolve the 502 error right away, as the container can now communicate with Nginx and the database.

Better Long-Term Update Workflow (No Rebuild) #

Since you've already created a new image with docker commit, let's use Docker Compose to launch it properly—this ensures it automatically joins the right network and inherits all your existing config (volumes, environment variables, etc.).

1. Tweak your docker-compose.yml:
   Comment out the build section for the web service and add an image line pointing to your new image:

   services:
     web:
       # build:
       #   context: .
       #   dockerfile: Dockerfile.prod
       image: djangotango-on-docker_web
       command: gunicorn djangotango.wsgi:application --bind 0.0.0.0:8000
       volumes:
         - static_volume:/home/app/web/static
         - media_volume:/home/app/web/media
       expose:
         - 8000
       env_file:
         - ./.env.staging
       networks:
         service_network:
   

2. Restart the web service with Compose:
   Run this command to start your new image with all the correct network and config settings:

   sudo docker-compose up -d web
   

   Compose will handle stopping the old web container (if it's running) and starting the new one in the service_network automatically.

Even Better: Avoid docker commit Altogether #

Manually copying files to a container and committing a new image creates "dirty" images—they're not reproducible, since the changes aren't tracked in a Dockerfile. Here's a lighter alternative for code updates:

• Copy code directly to the running container:

  # Copy your updated code into the running web container
  sudo docker cp ./path/to/your/app/code djangotango-web:/home/app/web/
  # Restart Gunicorn to pick up the changes (no container restart needed)
  sudo docker exec djangotango-web pkill -HUP gunicorn
  

• For static/media files, since you're already using volumes, just update the files on your host in the mounted volume location—they'll sync to the container automatically.

A Quick Note on docker-compose rebuild #

I get your concern about image size, but if your Dockerfile is optimized (e.g., using multi-stage builds, cleaning up dependencies after install), rebuilds won't bloat your image unnecessarily. Plus, rebuilds create reproducible images that you can easily share or deploy elsewhere. It's worth considering for future updates if you can!

内容的提问来源于stack exchange，提问作者Megha Aggarwal