Docker節點高山8分段錯誤（核心轉儲）

Question

我被困在一整天的這個錯誤困難。當我試圖運行我的碼頭集裝箱時，出現了錯誤Segmentation fault (core dumped)。

所以重現這個錯誤我會提供我的環境和代碼。

下面首先是Dockerfile，沒有什麼特別的：

FROM node:8.1.3-alpine 

RUN apk add --no-cache --update krb5-dev alpine-sdk python 

RUN mkdir -p /usr/src/app 
WORKDIR /usr/src/app 

COPY package.json /usr/src/app/ 
RUN npm install 
COPY . /usr/src/app 

EXPOSE 3000 

CMD [ "npm", "start" ] 

問題是與調用我的npm start腳本，它總是失敗的具有此命令"test-prod": "mocha test/**/*",的npm run test-prod。如果我從npm中刪除這個起始站點的部署沒有錯誤。

const { describe, it, before, after } = require('mocha'); 
const request = require('supertest'); 

const app = require('../../../app.js'); 
const User = require('../../../models/User'); 

const agent = request.agent(app); 
//some tests 

我想，它可以與新的貓鼬4.11版，該請求權威性的約束，並通過在選項：

測試-PROD從第一次測試，這與supertest進口app.js開始反對，但是當我通過它，它警告我說，這是錯誤的：

the options [user] is not supported 
the options [pass] is not supported 

最後以下主要部分app.js：

require('dotenv').config(); 

const express = require('express'); 
const path = require('path'); 
const favicon = require('serve-favicon'); 
const logger = require('morgan'); 
const cookieParser = require('cookie-parser'); 
const bodyParser = require('body-parser'); 
const session = require('express-session'); 
const mongoose = require('mongoose'); 
const MongoStore = require('connect-mongo')(session); 

const routes = require('./routes'); 

const app = express(); 

const URI = process.env.NODE_ENV === 'development' || process.env.NODE_ENV === 'test' ? 'mongodb://localhost/mulibwanji' : process.env.MONGODB_URI; 

mongoose.connect(URI, { // In URI also I have user and pass as expected 
    useMongoClient: true, 
    user: 'login', 
    pass: 'pass', 
}); 

誤差和從碼頭工人日誌：

2017-07-10T18:53:49.796105113Z 
2017-07-10T18:53:49.802949762Z 
2017-07-10T18:53:49.814928711Z Local strategy authentication 
2017-07-10T18:53:49.826690115Z  Login 
2017-07-10T18:53:51.226982330Z Segmentation fault (core dumped) 
2017-07-10T18:53:51.258175441Z npm info lifecycle mulibwanji@0.0.0~test-prod: Failed to exec test-prod script 
2017-07-10T18:53:51.258270885Z npm ERR! code ELIFECYCLE 
2017-07-10T18:53:51.258406077Z npm ERR! errno 139 
2017-07-10T18:53:51.258445569Z npm ERR! mulibwanji@0.0.0 test-prod: `mocha test/**/*` 
2017-07-10T18:53:51.258519335Z npm ERR! Exit status 139 
2017-07-10T18:53:51.258539503Z npm ERR! 
2017-07-10T18:53:51.258579954Z npm ERR! Failed at the mulibwanji@0.0.0 test-prod script. 
2017-07-10T18:53:51.258617042Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 

而且堆棧跟蹤這裏：

0 info it worked if it ends with ok 
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 
2 info using npm@5.0.3 
3 info using node@v8.1.3 
4 verbose run-script [ 'prestart', 'start', 'poststart' ] 
5 info lifecycle mulibwanji@0.0.0~prestart: mulibwanji@0.0.0 
6 silly lifecycle mulibwanji@0.0.0~prestart: no script for prestart, continuing 
7 info lifecycle mulibwanji@0.0.0~start: mulibwanji@0.0.0 
8 verbose lifecycle mulibwanji@0.0.0~start: unsafe-perm in lifecycle true 
9 verbose lifecycle mulibwanji@0.0.0~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/usr/src/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
10 verbose lifecycle mulibwanji@0.0.0~start: CWD: /usr/src/app 
11 silly lifecycle mulibwanji@0.0.0~start: Args: [ '-c', 
11 silly lifecycle 'npm run build && npm run test-prod && npm run lint && npm run update-schema && node ./bin/www' ] 
12 silly lifecycle mulibwanji@0.0.0~start: Returned: code: 139 signal: null 
13 info lifecycle mulibwanji@0.0.0~start: Failed to exec start script 
14 verbose stack Error: mulibwanji@0.0.0 start: `npm run build && npm run test-prod && npm run lint && npm run update-schema && node ./bin/www` 
14 verbose stack Exit status 139 
14 verbose stack  at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:283:16) 
14 verbose stack  at emitTwo (events.js:125:13) 
14 verbose stack  at EventEmitter.emit (events.js:213:7) 
14 verbose stack  at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14) 
14 verbose stack  at emitTwo (events.js:125:13) 
14 verbose stack  at ChildProcess.emit (events.js:213:7) 
14 verbose stack  at maybeClose (internal/child_process.js:897:16) 
14 verbose stack  at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5) 
15 verbose pkgid mulibwanji@0.0.0 
16 verbose cwd /usr/src/app 
17 verbose Linux 4.11.9-coreos 
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 
19 verbose node v8.1.3 
20 verbose npm v5.0.3 
21 error code ELIFECYCLE 
22 error errno 139 
23 error mulibwanji@0.0.0 start: `npm run build && npm run test-prod && npm run lint && npm run update-schema && node ./bin/www` 
23 error Exit status 139 
24 error Failed at the mulibwanji@0.0.0 start script. 
24 error This is probably not a problem with npm. There is likely additional logging output above. 
25 verbose exit [ 139, true ] 

我會感謝這麼多的任何建議，謝謝。

Answer 1

似乎bcrypt已經上傳了與musl alpine libc不兼容的bcrypt的預編譯版本。我增加了以下我Dockerfile：

RUN npm rebuild bcrypt --build-from-source

它自動地開始工作。我也無法恢復到7，因爲那時我遇到了一些與二進制不兼容的問題。

bcrypt可能是您的案例中的次要依賴項，解釋您的行爲。

對我來說，它在7月7日停止工作。雖然bcrypt的最新版本是在2月份發佈的，但我仍然認爲可以「更新」發行版，也許他們在當天添加了預編譯版本，我不知道。