不使用Docker Compose连接Rails与Postgres容器的疑问及方法

Great question! Let's break down why connecting your Rails app container to Postgres without Docker Compose can feel tricky, and then walk through exactly how to make it work.

You're right that container isolation plays a big role, but there are a few other key reasons this feels cumbersome:

• Default bridge network limitations: The default bridge network (which both your containers are using, per your metadata) doesn't support DNS resolution by container name. That means you can't just use postgres as the host in your Rails config—you have to rely on the container's static IP (like 172.17.0.2 for your Postgres instance), which can change every time you restart the container.
• Manual environment variable syncing: Docker Compose automatically passes and manages shared environment variables between linked containers. Without it, you have to manually set all critical Postgres credentials (like POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB) when launching the Postgres container, then mirror those exact values in your Rails container's environment or database config.
• No built-in startup ordering: Compose handles starting dependent services in the right sequence (Postgres first, so the database is ready when Rails boots). Without it, you have to manually wait for Postgres to finish initializing before starting your Rails app, or add retry logic in your app to handle the database not being available immediately.
• Disjointed cleanup: Compose lets you tear down all related containers, networks, and volumes with one command. Without it, you have to track and remove each component individually if you want to start fresh.

Based on your container metadata, here's how to get your Rails and Postgres containers talking reliably:

First, create a custom Docker network (way better than default bridge) #

The default bridge network's lack of DNS is a major pain point. Let's make a custom network so we can use container names instead of flaky IP addresses:

docker network create rails-postgres-net

Launch the Postgres container with essential settings #

You'll need to set core Postgres environment variables and attach it to our custom network. Replace the placeholder values with your own:

docker run -d \
  --name postgres-db \
  --network rails-postgres-net \
  -e POSTGRES_USER=your_db_user \
  -e POSTGRES_PASSWORD=your_db_password \
  -e POSTGRES_DB=your_rails_app_development \
  -v postgres-data:/var/lib/postgresql/data \
  postgres:12

• --name postgres-db: Gives the container a stable, referenceable name for Rails to use.
• --network: Ensures it's on the same network as our Rails app for DNS resolution.
• -e flags: Set the credentials your Rails app will need to authenticate with Postgres.
• -v: Creates a persistent volume to keep your Postgres data safe when the container restarts.

Update your Rails app's database configuration #

Edit your Rails app's config/database.yml to use the Postgres container's name as the host, and match the credentials you set earlier:

development:
  adapter: postgresql
  encoding: unicode
  database: your_rails_app_development
  username: your_db_user
  password: your_db_password
  host: postgres-db  # This works because we're on the same custom network
  port: 5432

Start your Rails container on the same network #

Launch your Rails container, attach it to our custom network, and map ports so you can access the app from your host machine. If you have a Dockerfile for your Rails app, run:

docker run -d \
  --name rails-app \
  --network rails-postgres-net \
  -p 3000:3000 \
  your-rails-image-name

• --network: Ensures it can resolve postgres-db to the correct container IP via DNS.
• -p: Maps port 3000 on your host to the container's port 3000, so you can visit http://localhost:3000 in your browser.

Wait for Postgres to initialize before starting Rails (critical!) #

Postgres takes a few seconds to start up and create the initial database. If you launch Rails right away, it might fail to connect. You can either:

• Wait 10-15 seconds after starting Postgres before launching Rails, or
• Add a health check to your Postgres container to automate this, or
• Include a retry script in your Rails container to keep trying the connection until Postgres is ready.

Verify the connection #

To confirm everything works, fire up a Rails console inside your container and test the database connection:

docker exec -it rails-app rails c
> ActiveRecord::Base.connection # Should return a connection object without errors

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