Node.js docker compose控制台输出出现问题 问题

我在开发时运行了

docker compose up

，所以我只需要快速查看一下终端（使用集成vs代码终端），看看我的单元测试、lint作业和其他工作是否运行良好

如果我想

console.log

API中的某个东西，它会在终端中弹出，我可以从中进行调试

但是，从今天下午开始，我不再拥有来自所有容器的日志，而是拥有来自容器

transpiler

、

kibana

和

apm server

的日志

我想解决什么问题 我曾经用ctrl+s来触发linter和mocha容器（因为这两个容器都使用nodemon，所以修改文件会使它们输出），然后将typescripts文件构建到js（监视模式下的transpiler）中，并让它们将所有内容输出到终端

没有来自

api

，

mocha

或

linter

的输出，即使我在代码中放了一些

console.log

我没有做任何重大更新，只是更换了计算机（都是安装了docker的ubuntu linux），我不知道如何解决这个问题

docker-compose.yml文件 Dockerfile 数据样本 当我运行docker up时，所有输出都正常：

mongo            | 2019-03-22T23:11:26.048+0000 I NETWORK  [conn6] end connection 172.22.0.8:52266 (3 connections now open)
apm_server       | 2019-03-22T23:11:26.048Z     INFO    [request]       beater/v2_handler.go:96 error handling request  {"request_id": "77b88109-c7c0-41a2-a28c-2343a82862bd", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "172.22.0.8", "user-agent": "elastic-apm-node/2.6.0 elastic-apm-http-client/7.1.1", "error": "unexpected EOF"}
api              | [nodemon] app crashed
api              | error Command failed with exit code 1.
api              | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
mocha            | 
mocha            | 
mocha            | Express server listening on port 9000, in test mode
mocha            |   GET PING ressource
mocha            |     GET /api/v1/ ping/
mongo            | 2019-03-22T23:11:27.951+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39956 #8 (4 connections now open)
mongo            | 2019-03-22T23:11:27.961+0000 I NETWORK  [conn8] received client metadata from 172.22.0.2:39956 conn8: { driver: { name: "nodejs", version: "3.1.13" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.20.7-042007-generic" }, platform: "Node.js v10.15.3, LE, mongodb-core: 3.1.11" }
mongo            | 2019-03-22T23:11:28.051+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39958 #9 (5 connections now open)
mongo            | 2019-03-22T23:11:28.197+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39962 #10 (6 connections now open)
mocha            |       ✓ ping api (154ms)

是的，我知道那些日志显示了一些错误，但我主要关心的是它们仍然在终端中输出

但按ctrl+s组合键只会显示以下情况：（这是我真正的问题）：

我尝试过的（但没有成功）

• 移除所有容器
• 移除所有容器及其体积
• 删除所有容器及其卷和所有映像
• 重新启动
• 删除所有内容后重新生成（

  docker compose build

  ）
• 从简单终端运行

  docker compose up

  cmd，以确保vs代码集成终端不会出现问题
• 重新启动docker服务（

  sudo systemctl restart docker

  ）

---

当您重建所有内容时，npm包中的某个地方很可能发生了变化（可能是您不知道自己有依赖关系）

---

此外，您还说您更换了计算机在以前的计算机和操作系统上是否仍能按预期工作？

当您重建所有东西时，很可能在某个地方的npm包中发生了更改（可能是您不知道自己有依赖关系）你说你换了电脑，它在前一台电脑上是否仍能正常工作，而在另一台电脑上则无法检查，它正在工作。然而，我怀疑它是否来自npm软件包，原因有两个：第一，我有一个warn.lock文件，第二，我没有合并我所做的修改，并试图克隆master并从中重新启动，但同样的问题当你说diff computer但都是Linux。。。它们是同一个版本吗（Ubuntu？16 18？Centos 6 7？Ubuntu，一个16.04，另一个18.04，但事实上你是对的，我刚刚用master的Thread.lock再次尝试了，现在效果很好。我想我在从master克隆时忘记了构建，现在将尝试缩小导致问题的数据包的范围（现在我想起来了，我在工作中做了

纱线升级

，但没有重建，所以问题可能来自这次升级）。如果你想发布答案，我会接受，因为你解决了我的问题：）真棒很高兴听到你发现了问题

FROM mhart/alpine-node:10
ADD . /app
WORKDIR /app

RUN apk add --no-cache --virtual .gyp g++ libtool make python curl &&\
    yarn &&\
    yarn global add nodemon &&\
    apk del .gyp

mongo            | 2019-03-22T23:11:26.048+0000 I NETWORK  [conn6] end connection 172.22.0.8:52266 (3 connections now open)
apm_server       | 2019-03-22T23:11:26.048Z     INFO    [request]       beater/v2_handler.go:96 error handling request  {"request_id": "77b88109-c7c0-41a2-a28c-2343a82862bd", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "172.22.0.8", "user-agent": "elastic-apm-node/2.6.0 elastic-apm-http-client/7.1.1", "error": "unexpected EOF"}
api              | [nodemon] app crashed
api              | error Command failed with exit code 1.
api              | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
mocha            | 
mocha            | 
mocha            | Express server listening on port 9000, in test mode
mocha            |   GET PING ressource
mocha            |     GET /api/v1/ ping/
mongo            | 2019-03-22T23:11:27.951+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39956 #8 (4 connections now open)
mongo            | 2019-03-22T23:11:27.961+0000 I NETWORK  [conn8] received client metadata from 172.22.0.2:39956 conn8: { driver: { name: "nodejs", version: "3.1.13" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.20.7-042007-generic" }, platform: "Node.js v10.15.3, LE, mongodb-core: 3.1.11" }
mongo            | 2019-03-22T23:11:28.051+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39958 #9 (5 connections now open)
mongo            | 2019-03-22T23:11:28.197+0000 I NETWORK  [listener] connection accepted from 172.22.0.2:39962 #10 (6 connections now open)
mocha            |       ✓ ping api (154ms)

[10:59:15 PM] File change detected. Starting incremental compilation...
transpiler       | 
transpiler       | [10:59:15 PM] Found 0 errors. Watching for file changes.
transpiler       | 
apm_server       | 2019-03-22T22:59:40.309Z     INFO    [request]       beater/common_handlers.go:272   handled request {"request_id": "5948c9ee-c6fd-42ad-bd1e-acc259e1634c", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "172.22.0.11", "user-agent": "elastic-apm-node/2.6.0 elastic-apm-http-client/7.1.1", "response_code": 202}
kibana           | {"type":"response","@timestamp":"2019-03-22T22:59:44Z","tags":[],"pid":1,"method":"get","statusCode":302,"req":{"url":"/","method":"get","headers":{"user-agent":"curl/7.29.0","host":"localhost:5601","accept":"*/*"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":302,"responseTime":7,"contentLength":9},"message":"GET / 302 7ms - 9.0B"}