推荐最新

docker compose 从django链接chromadb 报错 HTTPConnectionPool Max retries exceeded with url如何修复？

Docker中有两个container，一个django，一个chroma向量数据库，从Django中连接chroma报错，下面是docker-compose.yml文件： version: '3.9' services: django: container_name: django build: context: ./app command: python manage.py runserver 0.0.0.0:8000 volumes: - ./app:/Users/apple/Docker/app/ ports: - '8000:8000' expose: - 8000 chroma: container_name: chroma image: ghcr.io/chroma-core/chroma:latest volumes: - index_data:/Users/apple/Docker/app/data ports: - '8989:8989' expose: - 8989 volumes: index_data: name: my-db-data 下面是Dockerfile文件 FROM python:3.9 WORKDIR /Users/apple/Docker/app ENV PYTHONDONTWRITEBYTECODE 1 ENV PYTHONUNBUFFERED 1 RUN pip install --upgrade pip COPY ./requirements.txt /Users/apple/Docker/app/requirements.txt RUN pip3 install -r requirements.txt COPY ./entrypoint.sh /Users/apple/Docker/app/entrypoint.sh COPY . /Users/apple/Docker/app/ EXPOSE 8000 ENTRYPOINT ["/Users/apple/Docker/app/entrypoint.sh"] 从Django中连接chroma向量数据看，代码如下： from rest_framework.decorators import api_view from rest_framework.response import Response import chromadb from chromadb.config import Settings chroma_client = chromadb.HttpClient( host='localhost', port=8989, settings=Settings(allow_reset=True, anonymized_telemetry=False)) @api_view(['GET']) def index(request): sample_collection = chroma_client.get_or_create_collection(name="sample_collection") print(sample_collection) return Response({ 'info': 'Hello world.' }) 报错如下： urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='127.0.0.1', port=8989): Max retries exceeded with url: /api/v1/collections (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused')) Docker的容器运行情况： CONTAINER ID PORTS. NAMES 2710918946b0 0.0.0.0:8000->8000/tcp django 18ee5e4e3a7d 8000/tcp, 0.0.0.0:8989->8989/tcp chroma 请各位大佬帮忙看看，谢谢。

浏览量323

代码日记

在 docker-compose.yml 文件中配置 env_file 来指定环境变量文件，但是不生效？

如下是 docker-compose.yml 文件： services: node: image: node env_file: - .dev.env environment: - MY_NAME=${MY_NAME} 当使用下面的命令启动服务时，会读取不到 MY_NAME 这个变量： docker-compose up 但是使用 "--env-file" 选项就能使用环境变量文件： docker-compose --env-file=.dev.env up 这是什么情况？

浏览量297

Yourselffff

docker compose 怎么单独执行某一部分的命令？

我现在docker-compose的yml大概是这样的： version: "3.9" services: server-pc: container_name: test-server-pc image: "test-server-pc:2.4.2" environment: - TZ=Asia/Shanghai restart: always networks: - 'cnit-net-main' ports: - '8080:8080' volumes: - "/cnit-serv/test/server-pc/apl-log:/apl-log" - "/cnit-serv/test/server-pc/apl-configs:/apl-configs" - "/cnit-serv/test/server-pc/apl-wx-pay-cert:/apl-wx-pay-cert" - "/cnit-serv/test/server-pc/apl-public:/apl-public" - "/cnit-serv/test/server-pc/apl-static:/apl-static" - "/cnit-serv/test/server-pc/apl-ftl-templates:/apl-ftl-templates" - "/cnit-serv/test/server-pc/apl-upload:/apl-upload" - "/cnit-serv/test/server-pc/apl-webapp:/apl-webapp" privileged: true nginx: container_name: cnit-nginx image: "nginx" environment: - TZ=Asia/Shanghai restart: always networks: - 'cnit-net-main' ports: - '80:80' - '443:443' volumes: - "/cnit-serv/nginx/www/html:/usr/share/nginx/html" - "/cnit-serv/nginx/config/certs/:/etc/nginx/certs" - "/cnit-serv/nginx/config/nginx.conf:/etc/nginx/nginx.conf" - "/cnit-serv/nginx/config/conf.d:/etc/nginx/conf.d" - "/cnit-serv/nginx/logs:/var/log/nginx" - "/cnit-serv/test/front-pc/ver-2-4-2/dist:/srv/test/pc-admin" - "/cnit-serv/test/front-hp:/srv/test/www" privileged: true depends_on: - "server-pc" networks: cnit-net-main: external: true 简单来说呢，就是启动一个后台服务和一个前台服务。我正常重启的流程是，发布新的代码后，修改"test-server-pc:2.4.2"和"front-pc/ver-2-4-2"的版本号，之后停止服务，重新启动。重新启动的命令是： cd /cnit-serv/test/docker-compose/ docker compose down docker compose up -d 那我现在有一个问题就是，我只改了前台，我的后台并没有改动，所以我只想把前台从"/cnit-serv/test/front-pc/ver-2-4-2/dist:/srv/test/pc-admin"变成"/cnit-serv/test/front-pc/ver-2-4-3/dist:/srv/test/pc-admin"，那我该怎么在不停止后台服务的情况下，重启前台呢？

浏览量321

全能人才

nodejs项目使用docker部署为何失败？

nodejs使用thinkjs开发的项目docker-compose部署失败我在用docker-compose部署一个node.js项目时遇见的无法部署，该项目之前使用pm2直接部署在宿主机是可以正常运行的，项目使用了thinkjs框架，下面的是我的docker-compose文件： services: node: image: node:18.17.1 volumes: - /data/jxxw/node/h5-api/:/data/jxxw/node working_dir: /data/jxxw/node command: npm start ports: - "8362:8362" h5-api是我把node项目解压之后的文件夹,执行docker-compose up -d之后发现容器未启动，查看logs获得如下提示： > jxxw-api@1.0.0 start > node production.js node:internal/modules/cjs/loader:1080 throw err; ^ Error: Cannot find module 'thinkjs' Require stack: - /data/jxxw/node/production.js at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) at Module._load (node:internal/modules/cjs/loader:922:27) at Module.require (node:internal/modules/cjs/loader:1143:19) at require (node:internal/modules/cjs/helpers:121:18) at Object. (/data/jxxw/node/production.js:2:21) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Module._load (node:internal/modules/cjs/loader:960:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) { code: 'MODULE_NOT_FOUND', requireStack: [ '/data/jxxw/node/production.js' ] } Node.js v18.17.1 看提示是未读取到thinkjs的依赖，据node开发同学反馈他的打包流程如下： 1.npm install 2.npm pack 之后就把生成的tgz文件给到我这边，我尝试过写dockerfile文件解决，如下： # 使用官方 Node.js 镜像 FROM node:18.17.1 # 设置工作目录 WORKDIR /data/jxxw/node # 将当前目录下的所有内容都复制到位于 /app 的容器中 COPY . /data/jxxw/node # 安装项目依赖 RUN npm install # 暴露端口，供外部访问 EXPOSE 8362 提示install失败： => ERROR [4/4] RUN npm install 1542.3s ------ > [4/4] RUN npm install: 1542.3 npm ERR! code ECONNREFUSED 1542.3 npm ERR! syscall connect 1542.3 npm ERR! errno ECONNREFUSED 1542.3 npm ERR! FetchError: request to https://registry.npmjs.org/ava failed, reason: connect ECONNREFUSED 104.16.28.34:443 1542.3 npm ERR! at ClientRequest. (/usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14) 1542.3 npm ERR! at ClientRequest.emit (node:events:514:28) 1542.3 npm ERR! at TLSSocket.socketErrorListener (node:_http_client:501:9) 1542.3 npm ERR! at TLSSocket.emit (node:events:526:35) 1542.3 npm ERR! at emitErrorNT (node:internal/streams/destroy:151:8) 1542.3 npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:116:3) 1542.3 npm ERR! at process.processTicksAndRejections (node:internal/process/task_queues:82:21) 1542.3 npm ERR! FetchError: request to https://registry.npmjs.org/ava failed, reason: connect ECONNREFUSED 104.16.28.34:443 1542.3 npm ERR! at ClientRequest. (/usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14) 1542.3 npm ERR! at ClientRequest.emit (node:events:514:28) 1542.3 npm ERR! at TLSSocket.socketErrorListener (node:_http_client:501:9) 1542.3 npm ERR! at TLSSocket.emit (node:events:526:35) 1542.3 npm ERR! at emitErrorNT (node:internal/streams/destroy:151:8) 1542.3 npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:116:3) 1542.3 npm ERR! at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { 1542.3 npm ERR! code: 'ECONNREFUSED', 1542.3 npm ERR! errno: 'ECONNREFUSED', 1542.3 npm ERR! syscall: 'connect', 1542.3 npm ERR! address: '104.16.28.34', 1542.3 npm ERR! port: 443, 1542.3 npm ERR! type: 'system', 1542.3 npm ERR! requiredBy: '.' 1542.3 npm ERR! } 1542.3 npm ERR! 1542.3 npm ERR! If you are behind a proxy, please make sure that the 1542.3 npm ERR! 'proxy' config is set properly. See: 'npm help config' 1542.3 1542.3 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-01-30T14_55_34_130Z-debug-0.log ------ Dockerfile:8 -------------------- 6 | COPY . /data/jxxw/node 7 | # 安装项目依赖 8 | >>> RUN npm install 9 | # 暴露 8000 端口，供外部访问 10 | EXPOSE 8362 -------------------- ERROR: failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1 ERROR: Service 'node' failed to build : Build failed 文件夹里面的内容： "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20241012/51442a17882aca0ab26a493929096900.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20241012/f8f4ac3f0bf1276f5a936c80d592112c.png) 麻烦大佬指点为何，个人理解是thinkjs没有被正确的install，如果我想只写docker-compose文件不写dockerfile文件应该如何操作

浏览量224

喝一杯吧可以吗

gitlab迁移到docker同时恢复备份失败应该如何解决？

最近公司要把在云服务器的代码仓库迁移到内网云服务器的gitlab是直接运行的，在内网要求使用docker部署，两边的版本都是gitlab ce 16.6.2 首先：我在云服务器通过命令生成了备份压缩包： gitlab-rake gitlab:backup:create 接着把压缩包下载到内网服务器，使用docker-compose运行gitlab。 docker-compose.yml version: '3' services: gitlab: container_name: gitlab image: gitlab/gitlab-ce:16.6.2-ce.0 restart: always ports: - "80:80" environment: - TZ=Asia/Shanghai volumes: - /data/gitlab/config:/etc/gitlab - /data/gitlab/logs:/var/log/gitlab - /data/gitlab/data:/var/opt/gitlab networks: - gitlab_network networks: gitlab_network: driver: bridge 容器成功启动，并且可以正常访问复制 gitlab-secrets.json和gitlab.rb文件到/data/gitlab/config，重启容器生效然后复制备份文件压缩包1706197160_2024_01_25_16.6.2_gitlab_backup.tar到/data/gitlab/data/backups 进入容器查看git用户的uid，之后给压缩包赋所有权到git用户之后执行 gitlab-rake gitlab:backup:restore BACKUP=1706197160_2024_01_25_16.6.2 提示如下： 2024-01-26 11:58:25 UTC -- Unpacking backup ... tar: Skipping to next header tar: Skipping to next header tar: Skipping to next header tar: A lone zero block at 6596142 tar: Exiting with failure status due to previous errors 2024-01-26 11:58:29 UTC -- Unpacking backup failed 2024-01-26 11:58:29 UTC -- Deleting backup and restore PID file ... done 查看/data/gitlab/logs/gitlab-rails下面的backup_json.log： {"severity":"INFO","time":"2024-01-26T11:58:25.470Z","correlation_id":null,"message":"Unpacking backup ... "} {"severity":"INFO","time":"2024-01-26T11:58:29.994Z","correlation_id":null,"message":"Unpacking backup failed"} 我不知道从哪里可以获取更多更详细的错误信息，请告诉我一下，我去获取更详细的错误信息。或者有遇见过相同问题的可以麻烦解答一下，感谢

浏览量217

元气满满才怪啊

debian12 如何使用 apt 一键安装 docker-compose V2 版本？

debian12 如何使用 apt 一键安装 docker-compose V2 版本？仓库里面自带的，还是 python 写的 v1 版本，我要安装 golang 写的 v2 版本 ops@es-redis-20240228:~/opt/redis$ sudo apt install docker-compose Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: docker-buildx-plugin docker-compose-plugin libltdl7 libslirp0 pigz slirp4netns Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: binutils binutils-common binutils-x86-64-linux-gnu cgroupfs-mount containerd criu docker.io libbinutils libctf-nobfd0 libctf0 libgprofng0 libintl-perl libintl-xs-perl libjansson4 libmodule-find-perl libmodule-scandeps-perl libnet1 libnftables1 libnl-3-200 libproc-processtable-perl libprotobuf32 libsort-naturally-perl libterm-readkey-perl needrestart python3-attr python3-distro python3-distutils python3-docker python3-dockerpty python3-docopt python3-dotenv python3-json-pointer python3-jsonschema python3-lib2to3 python3-protobuf python3-pyrsistent python3-rfc3987 python3-texttable python3-uritemplate python3-webcolors python3-websocket runc tini Suggested packages: binutils-doc containernetworking-plugins docker-doc aufs-tools btrfs-progs debootstrap rinse rootlesskit xfsprogs zfs-fuse | zfsutils-linux needrestart-session | libnotify-bin iucode-tool python-attr-doc python-jsonschema-doc The following packages will be REMOVED: containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras The following NEW packages will be installed: binutils binutils-common binutils-x86-64-linux-gnu cgroupfs-mount containerd criu docker-compose docker.io libbinutils libctf-nobfd0 libctf0 libgprofng0 libintl-perl libintl-xs-perl libjansson4 libmodule-find-perl libmodule-scandeps-perl libnet1 libnftables1 libnl-3-200 libproc-processtable-perl libprotobuf32 libsort-naturally-perl libterm-readkey-perl needrestart python3-attr python3-distro python3-distutils python3-docker python3-dockerpty python3-docopt python3-dotenv python3-json-pointer python3-jsonschema python3-lib2to3 python3-protobuf python3-pyrsistent python3-rfc3987 python3-texttable python3-uritemplate python3-webcolors python3-websocket runc tini 0 upgraded, 44 newly installed, 4 to remove and 2 not upgraded. Need to get 75.6 MB of archives. After this operation, 32.6 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:2 https://deb.debian.org/debian bookworm/main amd64 runc amd64 1.1.5+ds1-1+deb12u1 [2710 kB] Get:3 https://deb.debian.org/debian bookworm/main amd64 containerd amd64 1.6.20~ds1-1+b1 [25.9 MB] Get:4 https://deb.debian.org/debian bookworm/main amd64 tini amd64 0.19.0-1 [255 kB] Get:5 https://deb.debian.org/debian bookworm/main amd64 docker.io amd64 20.10.24+dfsg1-1+b3 [36.2 MB] Get:6 https://deb.debian.org/debian bookworm/main amd64 binutils-common amd64 2.40-2 [2487 kB] Get:7 https://deb.debian.org/debian bookworm/main amd64 libbinutils amd64 2.40-2 [572 kB] Get:8 https://deb.debian.org/debian bookworm/main amd64 libctf-nobfd0 amd64 2.40-2 [153 kB] Get:9 https://deb.debian.org/debian bookworm/main amd64 libctf0 amd64 2.40-2 [89.8 kB] Get:10 https://deb.debian.org/debian bookworm/main amd64 libgprofng0 amd64 2.40-2 [812 kB]

浏览量201

饼干爱折腾

docker-compose.yml文件部署MySQL时出现错误?

在Ubuntu中通过docker-compose部署MySQL时无法部署；docker-compose.yml文件如下： version: '3' services: mysql: restart: always image: mysql:8.2 network_mode: bridge container_name: mysql environment: MYSQL_ROOT_PASSWORD: root123 command: --character-set-server=utf8mb4 --collation-server=utf8mb4_general_ci --explicit_defaults_for_timestamp=true --lower_case_table_names=1 --max_allowed_packet=128M volumes: - /etc/localtime:/etc/localtime:ro - /data/docker/mysql/mysql:/var/lib/mysql - /data/docker/mysql/etc:/etc/mysql:ro ports: - 3306:3306 我的步骤如下： 1.注释挂载，直接启动mysql 成功 2.复制容器中的/var/lib/mysql到宿主机我希望挂载的地方 3.复制/etc/mysql ，然后编写my.cnf放到宿主机/data/docker/mysql/etc/mysql/conf.d下 4.删除镜像 5.打开注释错误如下： 2024-01-21 12:00:35+08:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.2.0-1.el8 started. 2024-01-21 12:00:35+08:00 [ERROR] [Entrypoint]: mysqld failed while attempting to check config command was: mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_general_ci --explicit_defaults_for_timestamp=true --lower_case_table_names=1 --max_allowed_packet=128M --verbose --help --log-bin-index=/tmp/tmp.5xbHMoySK8 mysqld: Can't read dir of '/etc/mysql/conf.d/' (OS errno 2 - No such file or directory) mysqld: [ERROR] Stopped processing the 'includedir' directive in file /etc/my.cnf at line 36. mysqld: [ERROR] Fatal error in defaults handling. Program aborted!

浏览量170

走你啊啊啊啊啊

docker-compose中mysql数据丢失?

docker-compose挂载mysql，mysql老是重启并且数据丢失 docker-compose.yml文件 version: '3' services: mysql: # 服务名称 image: mysql:8.0.33 # 或其它mysql版本 container_name: mysql # 容器名称 environment: - MYSQL_ROOT_PASSWORD=123456 # root用户密码 # - TZ=Asia/Shanghai # 设置容器时区我这里通过下面挂载方式同步的宿主机时区和时间了,这里忽略 volumes: - /home/docker/mysql/log:/var/log/mysql # 映射日志目录，宿主机:容器 - /home/docker/mysql/data:/var/lib/mysql # 映射数据目录，宿主机:容器 - /home/docker/mysql/conf.d:/etc/mysql/conf.d # 映射配置目录，宿主机:容器 # - /etc/localtime:/etc/localtime:ro # 让容器的时钟与宿主机时钟同步，避免时间的问题，ro是read only的意思，就是只读。 ports: - 3306:3306 # 指定宿主机端口与容器端口映射关系，宿主机:容器 restart: always # 容器随docker启动自启 /home/docker/mysql/conf.d文件 ###### [client]配置模块 ###### [client] default-character-set=utf8mb4 socket=/var/lib/mysql/mysql.sock ###### [mysql]配置模块 ###### [mysql] # 设置MySQL客户端默认字符集 default-character-set=utf8mb4 socket=/var/lib/mysql/mysql.sock ###### [mysqld]配置模块 ###### [mysqld] port=3306 user=mysql # 设置sql模式 sql_mode模式引起的分组查询出现*this is incompatible with sql_mode=only_full_group_by，这里最好剔除ONLY_FULL_GROUP_BY sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock server-id = 1 # MySQL8 的密码认证插件如果不设置低版本navicat无法连接 default_authentication_plugin=mysql_native_password # 禁用符号链接以防止各种安全风险 symbolic-links=0 # 允许最大连接数 max_connections=1000 # 服务端使用的字符集默认为8比特编码的latin1字符集 character-set-server=utf8mb4 # 创建新表时将使用的默认存储引擎 default-storage-engine=INNODB # 表名存储在磁盘是小写的，但是比较的时候是不区分大小写 lower_case_table_names=0 max_allowed_packet=16M # 设置时区 default-time_zone='+8:00' 启动方式：docker-compose up -d mysql 希望mysql不重启，数据不会丢失

浏览量167

三千米的偷感

Docker Compose 部署 MySQL 报错，如何解决？

使用docker-compose 部署 MySQL 报错 "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240925/cdfa6da3121d7979ad2dcfe2415f4e07.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240925/33721c12d42b1b44b9757bd036d50a51.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240925/558a4ff59a9aa185e9925c3d7fb588b2.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240925/9e1df08ab7fd091072ec8ba53fc34370.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240925/71d8d6e399aee7e829df5e9ee97170d5.png) docker-compose.yml mysql配置部分 mysql: image: mysql container_name: mysql environment: - MYSQL_ROOT_PASSWORD=123456 volumes: - /data/mysql/log:/var/log/mysql - /data/mysql/data:/var/lib/mysql - /data/mysql/conf.d:/etc/mysql/conf.d - /etc/localtime:/etc/localtime:ro ports: - 3306:3306 restart: always my.cnf文件 ###### [client]配置模块 ###### [client] default-character-set=utf8mb4 socket=/var/lib/mysql/mysql.sock ###### [mysql]配置模块 ###### [mysql] # 设置MySQL客户端默认字符集 default-character-set=utf8mb4 socket=/var/lib/mysql/mysql.sock ###### [mysqld]配置模块 ###### [mysqld] port=3306 user=mysql # 设置sql模式 sql_mode模式引起的分组查询出现*this is incompatible with sql_mode=only_full_group_by，这里最好剔除ONLY_FULL_GROUP_BY sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock server-id = 1 # MySQL8 的密码认证插件如果不设置低版本navicat无法连接 default_authentication_plugin=mysql_native_password # 禁用符号链接以防止各种安全风险 symbolic-links=0 # 允许最大连接数 max_connections=1000 # 服务端使用的字符集默认为8比特编码的latin1字符集 character-set-server=utf8mb4 # 创建新表时将使用的默认存储引擎 default-storage-engine=INNODB # 表名存储在磁盘是小写的，但是比较的时候是不区分大小写 –initialize --lower_case_table_names=1 max_allowed_packet=16M # 设置时区 default-time_zone='+8:00'

浏览量148

爱打瞌睡的三角龙

Docker 从另一个容器连接到 redis 容器时为什么报错 Name or service not known?

redisConnectOptions const redisConnectOptions: RedisConnectOptions = { hostname: "redis://redis-stack", port: 6379, }; docker-compose.yml redis-stack: image: redis/redis-stack:latest container_name: redis-stack ports: - "6379:6379" - "6380:8001" networks: - my-network docker log 2024-05-19 18:53:04 error: Uncaught (in promise) Error: failed to lookup address information: Name or service not known 2024-05-19 18:53:04 : await Deno.connect(dialOpts); 2024-05-19 18:53:04 ^ 2024-05-19 18:53:04 at async Object.connect (ext:deno_net/01_net.js:587:55) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:190:11) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7) 2024-05-19 18:53:04 at async RedisConnection.#connect (https://deno.land/x/redis@v0.32.0/connection.ts:222:7)

浏览量137