How to connect to a PostgreSQL container with Rails

Question

I have a Docker-file which is declaring my Ruby on Rails application with nginx and a PostgreSQL database.

I'm struggling to understand how my Rails application connects to my PostgreSQL container, because it doesn't connect at all.

I built the Docker-file linking the images:

web:
  build: .
  command: bundle exec puma -C config/puma.rb
  volumes:
    - /tmp:/tmp
    # - /log:/data
    - .:/my_project_folder
  links:
    - nginx
    - db

nginx:
  build: ./nginx
  volumes:
    - /tmp:/tmp
  ports:
    - 80:80

db:
  image: postgres
  environment:
      POSTGRES_PASSWORD: "Postgres2019!"
  ports:
    - "15432:5432"
  volumes:
    - /Users/fred/Documents/Postgres/data:/var/lib/postgresql/data

and configured my database.yml like:

default: &default
  adapter: postgresql
  encoding: unicode
  host: 0.0.0.0
  port: 15432
  # For details on connection pooling, see Rails configuration guide
  # https://guides.rubyonrails.org/configuring.html#database-pooling
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  username: postgres
  password: Postgres2019!
development:
  <<: *default
  database: mos_development

But whenever I try to run my application, Rails can't connect to the database returning

ActiveRecord::ConnectionTimeoutError

but when I check my containers everything is running fine:

CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS              PORTS                     NAMES
1cfbc010829a        project_web           "bundle exec puma -C…"   19 minutes ago      Up 13 minutes                                 project_web_1
1774e2b89452        postgres              "docker-entrypoint.s…"   20 minutes ago      Up 13 minutes       0.0.0.0:15432->5432/tcp   project_db_1
0ce7dbb6d735        project_nginx         "nginx -g 'daemon of…"   3 hours ago         Up 13 minutes       0.0.0.0:80->80/tcp        project_nginx_1

If my PostgreSQL container is running at 0.0.0.0:15432, then my Rails container should be able to connect to it also at 0.0.0.0:15432, right?

your rails container should not connect at 0.0.0.0:15432, it should either connect to db:5432 or <docker0-interface-ip-addr>:15432. also if you have a static docker host ip you can also use <docker-host-ip>:15432 — Munish
– Munish, Commented Feb 22, 2020 at 21:36

the Tin Man · Accepted Answer · 2020-02-23 23:07:51Z

6

Try this:

default: &default
  adapter: postgresql
  encoding: unicode
  host: db    # <-- change this line
  port: 15432
  # For details on connection pooling, see Rails configuration guide
  # https://guides.rubyonrails.org/configuring.html#database-pooling
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  username: postgres
  password: Postgres2019!
development:
  <<: *default
  database: mos_development

The Rails application is linked to db, db:15432.

edited Feb 23, 2020 at 23:07

the Tin Man

161k44 gold badges222 silver badges308 bronze badges

answered Feb 22, 2020 at 21:43

J-Jacques M

1,1188 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

the Tin Man · Accepted Answer · 2020-02-23 23:07:25Z

0

This is usually a problem with the Active Record configuration, not the database itself.

You can verify that your database has available connections by running heroku pg:info from the command line and looking at the connection count compared to the maximum count for your plan.

This error is usually caused when the Active Record pool size is set too low or when trying to share a small number of database connections across a larger number of worker processes.

You can play around with this:

pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 1 } %>

As far as this part of the quesstion is concerned:

If my postgres container is running at 0.0.0.0:15432 then my rails container should be connect to it also at 0.0.0.0:15432, right?

Yes you have to use:

 docker-host-ip:15432

edited Feb 23, 2020 at 23:07

the Tin Man

161k44 gold badges222 silver badges308 bronze badges

answered Feb 22, 2020 at 21:42

Umar Hayat

5,0812 gold badges18 silver badges28 bronze badges

2 Comments

Fred Novack Over a year ago

That is correct, I had to change this value to 1 and also had to set the host do "db" as reported on the next answer

Umar Hayat Over a year ago

@Frederico, changed the value from 5 to 1.

Daniel · Accepted Answer · 2020-02-24 05:00:55Z

0

If you have too many environment variables, you can set them in a env files. e.g.

# .env.docker
RAILS_MAX_THREADS=4
USERNAME=posgres
...
...

Then specify the .env.docker file in your docker-compose file by env_file:

db:
  image: postgres
  env_file: .env.docker
  environment:
      POSTGRES_PASSWORD: "Postgres2019!"
  ports:
    - "15432:5432"
  volumes:
    - /Users/fred/Documents/Postgres/data:/var/lib/postgresql/data
...
...

answered Feb 24, 2020 at 5:00

Daniel

8992 gold badges7 silver badges19 bronze badges

Comments

Trần Vũ Quốc Tiến · Accepted Answer · 2022-05-16 03:17:16Z

0

I had a same issue. Try this

default: &default
  adapter: postgresql
  encoding: unicode
  host: db # change this line
  port: 5432 # change this line too, use internal port
  # For details on connection pooling, see Rails configuration guide
  # https://guides.rubyonrails.org/configuring.html#database-pooling
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  username: postgres
  password: Postgres2019!
development:
  <<: *default
  database: mos_development

edited May 16, 2022 at 3:17

answered May 16, 2022 at 3:11

Trần Vũ Quốc Tiến

12 bronze badges

Comments

Mykhailo Matrosov · Accepted Answer · 2023-10-23 18:21:09Z

0

docker-compose create

docker-compose run --rm web bin/rails db:create

answered Oct 23, 2023 at 18:21

Mykhailo Matrosov

3013 silver badges4 bronze badges

Collectives™ on Stack Overflow

How to connect to a PostgreSQL container with Rails

5 Answers 5

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related