gpt4 book ai didi

docker - 由于多个错误,Docker上的Redis无法运行

转载 作者:行者123 更新时间:2023-12-02 18:17:28 25 4
gpt4 key购买 nike

我一直在尝试将Redis容器连接到我的节点应用程序容器,但出现以下错误。报告问题之前,请先解决。

docker-compose
version: "3"

services:
vote:
build: ./voting/.
ports:
- "3000:3000"
networks:
- front-tier
- back-tier

result:
build: ./result/.
ports:
- "3011:3011"
networks:
- front-tier
- back-tier

worker:
build:
context: ./service_worker/.
depends_on:
- "redis"
- "db"
networks:
- back-tier

redis:
image: redis:alpine
container_name: redis
ports: ["6379"]
networks:
- back-tier

db:
image: mongo:latest
container_name: db
networks:
- back-tier

volumes:
db-data:

networks:
front-tier:
back-tier:
docker-compose up
vote_1    | the app is running
vote_1 | events.js:292
vote_1 | throw er; // Unhandled 'error' event
vote_1 | ^
vote_1 |
vote_1 | Error: Redis connection to 0.0.0.0:6379 failed - connect ECONNREFUSED 0.0.0.0:6379
vote_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
vote_1 | Emitted 'error' event on RedisClient instance at:
vote_1 | at RedisClient.on_error (/usr/src/app/node_modules/redis/index.js:341:14)
vote_1 | at Socket.<anonymous> (/usr/src/app/node_modules/redis/index.js:222:14)
vote_1 | at Socket.emit (events.js:315:20)
vote_1 | at emitErrorNT (internal/streams/destroy.js:92:8)
vote_1 | at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
vote_1 | at processTicksAndRejections (internal/process/task_queues.js:84:21) {
vote_1 | errno: 'ECONNREFUSED',
vote_1 | code: 'ECONNREFUSED',
vote_1 | syscall: 'connect',
vote_1 | address: '0.0.0.0',
vote_1 | port: 6379
vote_1 | }
docker logs redis
1:C 17 Oct 2020 07:36:16.705 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 17 Oct 2020 07:36:16.706 # Redis version=6.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 17 Oct 2020 07:36:16.706 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 17 Oct 2020 07:36:16.708 * Running mode=standalone, port=6379.
1:M 17 Oct 2020 07:36:16.708 # Server initialized
1:M 17 Oct 2020 07:36:16.708 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 17 Oct 2020 07:36:16.709 * Ready to accept connections
当我尝试 docker exec -ti redis redis-server
13:C 17 Oct 2020 07:42:16.608 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
13:C 17 Oct 2020 07:42:16.608 # Redis version=6.0.8, bits=64, commit=00000000, modified=0, pid=13, just started
13:C 17 Oct 2020 07:42:16.608 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
13:M 17 Oct 2020 07:42:16.608 # Could not create server TCP listening socket *:6379: bind: Address in use
现在我认为这是在几个地方,我已经看到了redis-config文件的错误,但是如何在docker镜像中解决它,这在哪里都没有得到很好的解释。连接没有问题,但是问题在于redis的配置。我可以使用dns / ip从其他容器ping通该容器。我认为,如果无法听到错误的最后一部分,其中*:6379不能听到,如果编辑了conf文件和该文件,该应用程序将正常运行。

最佳答案

您正在从另一个具有redis地址的容器连接到0.0.0.0:6379容器。如果要向主机公开redis:6379容器端口,请使用docker服务名称redis或主机的ip。

关于docker - 由于多个错误,Docker上的Redis无法运行,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/64400812/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com