Docker+Rails启动Postgres服务失败：端口5432被占用求助

Hey there, let’s get that Postgres container up and running! The error you’re hitting is super common—your host machine’s port 5432 is already being used by another process, so Docker can’t bind to it for your dataimobi-engine_postgres_1 service. Here are a few straightforward fixes to try:

1. Kill the process using port 5432 #

First, let’s find out what’s hogging that port:

• Linux/macOS: Run this command in your terminal:

  lsof -i :5432
  

  Look for the PID column in the output—that’s the process ID of the app using 5432. Kill it with:

  kill -9 <PID_NUMBER>
  

• Windows: Open Command Prompt and run:

  netstat -ano | findstr :5432
  

  The last number in the result is the PID. Open Task Manager, go to the Details tab, find that PID, right-click, and select "End Task".

After killing the process, run sudo docker-compose up again to test if it works.

2. Change the port mapping in your Docker Compose file #

If you don’t want to kill the existing process (maybe you’re using a local Postgres instance), you can remap the port in your docker-compose.yml:

1. Open your docker-compose.yml file and find the Postgres service section. It’ll look something like this:

   services:
     postgres:
       image: postgres:latest
       ports:
         - "5432:5432" # This is the conflicting line
       # ... other configs
   

2. Change the host port to something unused, like 5433:

   ports:
     - "5433:5432"
   

3. Don’t forget to update your Rails config/database.yml to use the new port:

   default: &default
     adapter: postgresql
     encoding: unicode
     pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
     host: postgres
     port: 5433 # Match the new host port here
     username: <%= ENV['POSTGRES_USER'] %>
     password: <%= ENV['POSTGRES_PASSWORD'] %>
   

4. Restart your services with sudo docker-compose up --force-recreate to apply the changes.

3. Clean up leftover Docker containers #

Sometimes a stopped Postgres container might still be holding onto the port (even if it’s not running). Check for any old containers:

docker ps -a

If you see a Postgres container in the list, stop and remove it:

docker stop <CONTAINER_ID>
docker rm <CONTAINER_ID>

Then try starting your services again.

4. Stop a local Postgres service (if you have one installed) #

If you have Postgres installed directly on your machine (not via Docker), it’s probably using port 5432 by default. Stop that service:

• Linux:

  sudo systemctl stop postgresql
  # To prevent it from starting on boot (optional):
  sudo systemctl disable postgresql
  

• macOS (if installed via Homebrew):

  brew services stop postgresql
  

• Windows: Open Services (search for "Services" in the start menu), find "PostgreSQL", right-click, and select "Stop".

After trying any of these steps, your dataimobi-engine_postgres_1 service should start up without the port conflict error.

内容的提问来源于stack exchange，提问作者Hemershon Silva