当我启动 Docker 容器时docker-compose up
,它像往常一样启动,但最终容器自动退出,而我可以看出详细日志中没有任何有用的内容。
当我跑步时docker-compose up --entrypoint run-tests.sh
与相同的docker-compose.yml
配置(具有相同的入口点集)和相同的 Dockerfile,Docker 容器会自行“正常停止”并停止所有容器。
不良行为似乎来自于跑步docker-compose up
而不是等价的docker-compose run
.
该容器在关闭之前似乎会停留不同的时间。在一个例子中,它持续了 7 分钟,而在其他例子中,时间则不同。
有谁知道如何解决这个问题?
Docker 版本:
Docker version 1.9.0, build 76d6bc9
docker-compose version: 1.5.0
docker-machine version 0.5.0 (HEAD)
The docker-compose --verbose up
log:
docker-compose --verbose --project-name monkeycore up monkeycore-autotest
... lots of startup log (let me know if you need to see this) ...
# Scala Play1 Framework tests, not likely relevant
monkeycore-autotest_1 | ~ MonkeyTest... PASSED 30s
monkeycore-autotest_1 | ~ WhateverDataTest... PASSED 33s
monkeycore-autotest_1 | ~ SauceTest... PASSED 1 min 44s
Gracefully stopping... (press Ctrl+C again to force)
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={u'label': [u'com.docker.compose.project=monkeycore', u'com.docker.compose.oneoff=False']})
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 2 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'617bf28c3f7ae3779f383f7e2a96f66e552e92f755a15d07ac6b73329ba3860f')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'',
u'Args': [u'-c', u'build.sh && play auto-test'],
u'Config': {u'AttachStderr': False,
u'AttachStdin': False,
u'AttachStdout': False,
u'Cmd': None,
u'CpuShares': 0,
u'Cpuset': u'',
u'Domainname': u'',
u'Entrypoint': [u'bash', u'-c', u'build.sh && play auto-test'],
...
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'4963e9287ed10d587a79f57a52eaf86c07c6947b2119072bd5d68a3ed0eb161e')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'',
u'Args': [u'/usr/local/etc/redis/redis.conf'],
u'Config': {u'AttachStderr': False,
u'AttachStdin': False,
u'AttachStdout': False,
u'Cmd': None,
u'CpuShares': 0,
u'Cpuset': u'',
u'Domainname': u'',
u'Entrypoint': [u'redis-server',
...
Stopping monkeycore_monkeycore-autotest_1 ...
compose.cli.verbose_proxy.proxy_callable: docker stop <- (u'617bf28c3f7ae3779f383f7e2a96f66e552e92f755a15d07ac6b73329ba3860f', timeout=10)
Stopping monkeycore_monkeycore-autotest_1 ... done
ERROR: compose.cli.main.main: Couldn't connect to Docker daemon - you might need to run `docker-machine start default`.
docker-compose.yml
:
monkeycore-base:
build: ../
dockerfile: "docker/monkeycore/Dockerfile"
ports:
- "8000:8000"
- "8082:8082"
- "9000:9000"
stdin_open: true
tty: true
working_dir: "/path/to/dir"
volumes:
- src:dest
environment:
LOTS_OF_ENVIRONMENT_VARIABLES: "defined"
monkeycore-autotest:
extends:
service: monkeycore-base
links:
- redis
entrypoint: "run-tests.sh"
redis:
build: ./redis
ports:
- "6379:6379"