基本docker compose命令超时错误
我看到了一个奇怪的问题,基本的基本docker compose命令超时错误,docker,docker-compose,docker-for-mac,Docker,Docker Compose,Docker For Mac,我看到了一个奇怪的问题,基本的docker编写了ps和down超时等命令 $ docker-compose ps ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consider setting CO
docker编写了ps
和down
超时等命令
$ docker-compose ps
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
没有理由认为这个过程需要60秒,通常不到10秒
我发现了一个stackoverflow帖子,但是docker ps似乎工作得很好,所以我认为它与docker compose特别相关。我还发现了其他一些相同错误的实例,但没有解决方案,唯一的建议是增加超时,这对我没有帮助
这是我的docker撰写文件:
---
version: '3.7'
services:
assets:
build:
context: .
args:
NPM_TOKEN: "${NPM_TOKEN}"
IS_LCL: "TRUE"
container_name: foobar_assets
volumes:
- .:/app:delegated
- /app/node_modules
- "${MESSAGING_PATH:-./node_modules/@foobar/baz}:/app/local_modules/@foobar/baz"
ports:
- "4005:4005"
# - "8888:8888"
env_file:
- .env
- .env-overrides
healthcheck:
test: curl -f http://localhost:4005/assets-manifest.json && echo 'assets are ready!'
interval: 2s
timeout: 1s
retries: 100
entrypoint: ['./rsync-entrypoint.sh']
command: ['/usr/local/bin/npm', 'run', 'dev:assets']
init: true
bff:
build:
context: .
args:
NPM_TOKEN: "${NPM_TOKEN}"
IS_LCL: "TRUE"
volumes:
- .:/app:delegated
- /app/node_modules
container_name: foobar_bff
links:
- redis
ports:
- "4010:4010"
- "9231:9231"
env_file:
- .env
- .env-overrides
depends_on:
- assets
entrypoint: ['./rsync-entrypoint.sh']
command: ['/usr/local/bin/npm', 'run', 'dev:server']
init: true
redis:
image: redis:2.8
container_name: foobar_redis
networks:
default:
external:
name: lcl.foobar.io
我正在运行Docker for Mac 2.1.0.3,并尝试重新启动它以及整个Mac。这暂时解决了问题,但随后问题再次出现。服务docker restart
应该会重新启动docker引擎。我正在docker for mac上运行,因此我使用docker desktop(如果相关,请使用v2.1.0.3)重新启动,但重新启动没有帮助。在这种情况下,您可以粘贴docker文件/docker compose.yml吗?@daudnadeem确定,只是补充一下你肯定curl-fhttp://localhost:4005/assets-manifest.json&&echo“资产已准备就绪!”代码>有效吗?从错误来看,这似乎是超时。服务docker restart
应该会重新启动docker引擎。我正在docker for mac上运行,所以我使用docker desktop(v2.1.0.3,如果相关的话)重新启动,但重新启动没有帮助。在这种情况下,你能粘贴docker文件/docker compose.yml吗?@daudnadeem当然,只是补充一下你肯定curl-fhttp://localhost:4005/assets-manifest.json&&echo“资产已准备就绪!”代码>有效吗?从错误来看,这似乎是超时。