aerospike-client-nodejs: Docker alpine-10 with aerospike not working

My docker file is -


RUN mkdir -p /usr/src/app

WORKDIR /usr/src/app

COPY package.json ./

RUN apk add --no-cache python2 make gcc g++ git libtool autoconf automake linux-headers \
openssl-dev zlib-dev libuv-dev

RUN git clone && \
  cd aerospike-client-c && \
  git checkout --detach 4.3.20 && \
  git submodule update --init && \
  make EVENT_LIB=libuv

RUN npm install

VOLUME ["./logs"]

COPY . .


CMD [ "npm", "start" ]

On docker build, getting error -

make: *** [ ebf8c619d512e7a1a724a0ecb06ec5eec50df7dc.intermediate] Error 1
rm ebf8c619d512e7a1a724a0ecb06ec5eec50df7dc.intermediate
make: Leaving directory '/usr/src/app/node_modules/aerospike/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.4.0-1077-aws
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/src/app/node_modules/aerospike
gyp ERR! node -v v10.15.3
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! errno 1
npm ERR! aerospike@3.10.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the aerospike@3.10.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.```

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 16 (8 by maintainers)

Most upvoted comments

These are not errors but warnings that can be ignored. During startup, the client tries to check the OS network send/receive buffer sizes using the net.core.wmem_max/net.core.rmem_max system interfaces, which doesn’t work inside a Docker container. So the client falls back to using reasonable default values.