dockerize NestJS and TypeORM

Question

i have this Dockerfile :

FROM node:12

WORKDIR /usr/src/app

COPY package*.json ./

RUN npm install

COPY . .

CMD [ "npm", "start"]

and docker-compose.yml looks like that :

version: '3.1'

services:

      db:
        image: postgres
        restart: always
        volumes:
          - ./db-data:/var/lib/postgresql/data
        environment:
          POSTGRES_PASSWORD: root
        ports:
          - 5432:5432
      node:
        build: .
        volumes:
          - ./public/storage/files:/usr/app/public/storage/files
        env_file: .env
        restart: always
        ports:
          - '8080:8080'

When projects starts it uses ormconfig.json

{
  "type": "postgres",
  "host": "localhost",
  "port": 5432,
  "username": "postgres",
  "database": "postgres",
  "password": "root",
  "synchronize": true,
  "logging": true,
  "entities": ["dist/**/*.entity.js"]
}

But i have error when run it in docker

[Nest] 30   - 08/19/2020, 5:49:39 PM   [TypeOrmModule] Unable to connect to the database. Retrying (4)... +3003ms
node_1  | Error: connect ECONNREFUSED 127.0.0.1:5432

Help pls to fix it. Without docker it works perfectly.

Does postgres image start?

Mikko Ohtamaa
– Mikko Ohtamaa

2020-08-19 18:20:16 +00:00
Commented Aug 19, 2020 at 18:20 — Mikko Ohtamaa
– Mikko Ohtamaa, Commented Aug 19, 2020 at 18:20

MohamadrezaRahimianGolkhandani · Accepted Answer · 2020-08-19 22:21:52Z

4

Because when you use docker-compose they are not in each other localhost.

Actually they are in separate docker networks

so you have to set their network to a same network or calling them by their container_name

{
  "type": "postgres",
  "host": "db", // container name
  "port": 5432,
  "username": "postgres",
  "database": "postgres",
  "password": "root",
  "synchronize": true,
  "logging": true,
  "entities": ["dist/**/*.entity.js"]
}

A working example is shown below: Also mind that its not necessary to do networking manually as @Charles Desbiens said in comments

version: "3.5"

services:
  # Databases # #
  postgresql-test:
    container_name: postgresql-test
    image: postgres:11.2-alpine
    environment:
      POSTGRES_USER: ${POSTGRES_USER:-admin}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-changeme}
      POSTGRES_DB: ${POSTGRES_DB:-crud-node}
      PGDATA: /data/postgres
    ports:
      - 30001:5432
    networks:
      - test
...
  node:
    build:
      context: ./backend
      dockerfile: Dockerfile.dev
    image: backend:latest
    container_name: backend
    depends_on:
      - postgresql-test
    networks:
      - test
    ports:
      - 3000:3000
      - 9229:9229

...
networks:
  test:

Now you can use address: postgresql-test & port: 5432 to access your db inside your code

{
  "type": "postgres",
  "host": "postgresql-test",
  "port": 5432,
  "username": "admin",
  "database": "crud-node",
  "password": "changeme",
  "synchronize": true,
  "logging": true,
  "entities": ["dist/**/*.entity.js"]
}

ALSO you can take a look at this repo.

edited Aug 19, 2020 at 22:21

answered Aug 19, 2020 at 19:48

MohamadrezaRahimianGolkhandani

8487 silver badges13 bronze badges

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

3 Comments

Charles Desbiens Over a year ago

You don't need to manually create a network and assign the services to it. You also don't need to rename the postgres service. Docker compose automatically creates a default network for all the services in a file and assigns the services to it. So, OP would just have to change the address he's using to connect to the database from 127.0.0.1 to db.

Roman Karpyshyn Over a year ago

@MohamadrezaRahimianGolkhandani thanks it works, could you tell me pls, why we have to define ports twice ports: - 3000:3000 - 9229:9229

MohamadrezaRahimianGolkhandani Over a year ago

your welcome, actually 9229 is the default debugger port for debugging nodejs with vscode, so it's better to expose this port in case of you want to debug your app inside container

Collectives™ on Stack Overflow

dockerize NestJS and TypeORM

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related