While using docker-compose, node application fails to connect to Redis

Question

I am running Ubuntu and trying to setup dev environment for node app, this is my docker-compose.yml:

version: "2"
services:
  redis:
    image: redis
    ports:
     - "6381:6379"
    volumes:
      - /var/lib/thinklog-queue:/data
  activity-service:
    build:
      context: ./activity-service
    command: yarn dev
    ports:
      - "3001:3001"
    environment:
      REDIS_QUEUE_URL: "redis://redis:6381"
    depends_on:
      - redis

and Dockerfile for the node app looks like this:

FROM node:9
WORKDIR /app
COPY package.json ./
COPY yarn.lock ./
RUN yarn install
COPY . .
EXPOSE 4000
CMD ["yarn", "start"]

I extend Redis connection string from env variable.

and when I run docker-compose build && docker-compose up inside logs I get this output from the node app:

activity-service_1 | Error: Redis connection to redis:6381 failed - connect ECONNREFUSED 172.20.0.2:6381

It appears that setup is right however there is something blocking intern connections to Redis. (inside this docker compose network)

Connections to this Redis instance from outside, e.g other shell session works just fine:

kuno@dell:~/code/THINKLOG/activity-service$ redis-cli -p 6381
127.0.0.1:6381> ping
PONG

I also tried mounting custom config like so (added new item to volume arrays for Redis inside docker-compose.yml):

  - ./redis.conf:/usr/local/etc/redis/redis.conf

which has bind line commented out as well as modifying it to be like so (the last address is one that docker-compose uses internally):

bind 192.168.1.100 10.0.0.1 172.20.0.2

Should I also mount in custom Redis configuration and configure Redis to allow connections within docker network?

nguyenkha · Accepted Answer · 2018-06-21 00:33:41Z

2

Change port to 6379 in the url REDIS_QUEUE_URL: "redis://redis:6379" 6381 is the port on the host IP not the redis container port.

answered Jun 21, 2018 at 0:33

nguyenkha

1,35612 silver badges13 bronze badges

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

1 Comment

Kunok Over a year ago

Yeah, just realized that and went to answer my own question and boom there you are. You are right, I got this wrong. I should call each of this redis differently inside docker-compose and use different hostname per instance instead of different ports.

Collectives™ on Stack Overflow

While using docker-compose, node application fails to connect to Redis

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related