Question

当我运行以下命令时，我期望退出代码为0，因为我的combined容器运行的测试已成功退出，退出代码为0。

docker-compose up --build --exit-code-from combined

不幸的是，即使我的combined容器中的测试成功运行并且我以0的退出代码退出该容器，我也始终收到137的退出代码（有关此操作的更多详细信息，请参见下文）。

以下是我的docker-compose版本：

docker-compose version 1.25.0, build 0a186604

根据此post，退出代码137可能是由于两个主要问题。

容器收到了docker stop，并且应用未正常处理SIGTERM
容器的内存不足（OOM）。

我知道137退出代码不是因为我的容器内存不足。当我运行docker inspect <container-id>时，我可以看到“ OOMKilled”为假，如代码片段所示。下面。我还为Docker Engine分配了6GB的内存，对我的应用程序来说足够了。

[
    {
        "Id": "db4a48c8e4bab69edff479b59d7697362762a8083db2b2088c58945fcb005625",
        "Created": "2019-12-12T01:43:16.9813461Z",
        "Path": "/scripts/init.sh",
        "Args": [],
        "State": {
            "Status": "exited",
            "Running": false,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false, <---- shows container did not run out of memory
            "Dead": false,
            "Pid": 0,
            "ExitCode": 137,
            "Error": "",
            "StartedAt": "2019-12-12T01:44:01.346592Z",
            "FinishedAt": "2019-12-12T01:44:11.5407553Z"
        },

我的容器也不从docker stop退出，因此我也不认为第一个原因与我的情况有关。

如何设置Docker容器

我有两个Docker容器：

b-db -包含我的数据库
b组合-包含我的Web应用程序和一系列测试，这些测试在容器启动并运行后便会运行。

我正在使用docker-compose.yml文件启动两个容器。

version: '3'
services:
    db:
        build:
            context: .
            dockerfile: ./docker/db/Dockerfile
        container_name: b-db
        restart: unless-stopped
        volumes:     
            - dbdata:/data/db
        ports:
            - "27017:27017"
        networks:
            - app-network

    combined:
        build:
            context: .
            dockerfile: ./docker/combined/Dockerfile
        container_name: b-combined
        restart: unless-stopped
        env_file: .env
        ports:
            - "5000:5000"
            - "8080:8080"
        networks:
            - app-network
        depends_on:
            - db

networks:
    app-network:
        driver: bridge

volumes:
    dbdata:
    node_modules:

以下是combined中docker-compose.yml服务的Dockerfile。

FROM cypress/included:3.4.1

WORKDIR /usr/src/app

COPY package*.json ./

RUN npm install

COPY . .

EXPOSE 5000

RUN npm install -g history-server nodemon

RUN npm run build-test

EXPOSE 8080

COPY ./docker/combined/init.sh /scripts/init.sh

RUN ["chmod", "+x", "/scripts/init.sh"]

ENTRYPOINT [ "/scripts/init.sh" ]

下面是我的init.sh文件中的内容。

#!/bin/bash
# Start front end server
history-server dist -p 8080 &
front_pid=$!

# Start back end server that interacts with DB
nodemon -L server &
back_pid=$!

# Run tests
NODE_ENV=test $(npm bin)/cypress run --config video=false --browser chrome

# Error code of the test
test_exit_code=$?

echo "TEST ENDED WITH EXIT CODE OF: $test_exit_code"

# End front and backend server
kill -9 $front_pid
kill -9 $back_pid

# Exit with the error code of the test
echo "EXITING SCRIPT WITH EXIT CODE OF: $test_exit_code"
exit "$test_exit_code"

以下是我的db服务的Dockerfile。它所做的就是将一些本地数据复制到Docker容器中，然后使用此数据初始化数据库。

FROM  mongo:3.6.14-xenial

COPY ./dump/ /tmp/dump/

COPY mongo_restore.sh /docker-entrypoint-initdb.d/

RUN chmod 777 /docker-entrypoint-initdb.d/mongo_restore.sh

下面是mongo_restore.sh中的内容。

#!/bin/bash
# Creates db using copied data
mongorestore /tmp/dump

下面是我运行docker-compose up --build --exit-code-from combined; echo $?时输出的最后几行。

...
b-combined | user disconnected
b-combined | Mongoose disconnected
b-combined | Mongoose disconnected through Heroku app shutdown
b-combined | TEST ENDED WITH EXIT CODE OF: 0 ===========================
b-combined | EXITING SCRIPT WITH EXIT CODE OF: 0 =====================================
Aborting on container exit...
Stopping b-combined   ... done
137

如上所示，令人困惑的是，由于我的所有测试均成功通过，因此测试和脚本以退出代码0结束，但是容器仍然以退出代码137退出。 < / p>

更令人困惑的是，当我从init.sh文件中注释掉以下行（运行我的Cypress集成测试）时，容器退出，退出代码为0，如下所示。 / strong>

NODE_ENV=test $(npm bin)/cypress run --config video=false --browser chrome

下面是我注释掉/从init.sh中删除上述行时收到的输出，这是运行Cypress集成测试的命令。

... b-combined | TEST ENDED WITH EXIT CODE OF: 0 =========================== b-combined | EXITING SCRIPT WITH EXIT CODE OF: 0 ===================================== Aborting on container exit... Stopping b-combined ... done 0

当测试成功运行时，如何让docker-compose返回零退出代码，而在测试失败时如何返回非零退出代码？

编辑：

在调试模式下运行以下docker-compose命令后，我注意到b-db似乎在关闭时遇到了一些麻烦，因此可能正在从Docker接收到SIGKILL信号。

docker-compose --log-level DEBUG up --build --exit-code-from combined; echo $?

根据以下输出，确实是这种情况吗？

... b-combined exited with code 0 Aborting on container exit... http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/json?limit=-1&all=1&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Db-property%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 3819 http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/json?limit=-1&all=0&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Db-property%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 4039 http://localhost:None "POST /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/attach?logs=0&stdout=1&stderr=1&stream=1 HTTP/1.1" 101 0 http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/json HTTP/1.1" 200 None Stopping b-combined ... Stopping b-db ... Pending: {<Container: b-db (0626d6)>, <Container: b-combined (196f3e)>} Starting producer thread for <Container: b-combined (196f3e)> http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} Pending: {<Container: b-db (0626d6)>} http://localhost:None "POST /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/wait HTTP/1.1" 200 32 http://localhost:None "POST /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/stop?t=10 HTTP/1.1" 204 0 http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "POST /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561bStopping b-combined ... done Finished processing: <Container: b-combined (196f3e)> Pending: {<Container: b-db (0626d6)>} Starting producer thread for <Container: b-db (0626d6)> http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/json HTTP/1.1" 200 None Pending: set() Pending: set() Pending: set() Pending: set() Pending: set() Pending: set() http://localhost:None "GET /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/json HTTP/1.1" 200 None http://localhost:None "POST /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/stop?t=10 HTTP/1.1" 204 0 http://localhost:None "POST /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/wait HTTP/1.1" 200 30 Stopping b-db ... done Pending: set() http://localhost:None "GET /v1.25/containers/0626d6bf49e5236440c82de4e969f31f4f86280d6f8f555f05b157fa53bae9b8/json HTTP/1.1" 200 None http://localhost:None "GET /v1.25/containers/196f3e622847b4c4c82d8d761f9f19155561be961eecfe874bbb04def5b7c9e5/json HTTP/1.1" 200 None 137

Answer 1

这可能是 RAM 的问题，我使用 Docker 首选项增加了内存。使用 docker-compose up 启动我的服务。服务器对我来说没有任何问题。

https://www.petefreitag.com/item/848.cfm

Answer 2

Docker 退出代码 137 意味着 Docker 没有足够的 RAM 来完成工作。

不幸的是，Docker 消耗了大量 RAM。

转到 Docker 桌面应用程序 > 首选项 > 资源 > 高级并增加内存 - 最好加倍。

Answer 3

此错误消息使我震惊：Aborting on container exit...

来自docker-compose docs：

-退出容器退出：如果已停止任何容器，则停止所有容器。

您是否正在使用此标志运行docker-compose？如果是这样，请考虑一下它的含义。

b-combined完成后，它只会退出。这意味着容器b-db也将被迫停止。即使b-combined返回了退出代码0，mongodb也无法正常处理b-db强制关闭。

编辑：我刚刚意识到您在命令行中有--exit-code-from。这意味着--abort-on-container-exit。

解决方案：b-db需要更多时间才能正常退出。使用docker compose up --timeout 600可以避免该错误。

Answer 4

不确定这是否可以解决您的问题，但是您可以尝试为合并的dockerfile添加FROM scratch吗？

Docker按顺序在Dockerfile中运行指令。 Dockerfile必须以FROM指令开头。 FROM指令指定要从中构建的基础映像。 FROM只能前面有一个或多个ARG指令，这些指令声明Dockerfile中FROM行中使用的参数。参考：https://docs.docker.com/v17.09/engine/reference/builder/#format

也不要使用docker-compose up 尝试分两个步骤进行操作，以收集有关问题发生位置的更多信息。

docker-compose --log-level DEBUG build
docker-compose --log-level DEBUG run

https://docs.docker.com/compose/reference/overview/ [根据评论编辑]

没有OOM异常时，Docker-compose退出代码为137

4 个答案: