Unsupported engine node / NPM only when building in Docker

Question

I have a dependency in my package.json which itself has the following dependency:

"node-rdkafka": "^2.5.0",

Using nvm on my local machine and setting my node version to 8.9.1, and my npm version is 5.5.1, I can successfully run

npm install node-rdkafka@2.7.1

But when running the same thing (i.e npm install) from within my docker image:

FROM node:10.13.0-alpine or FROM node:8.9.1-alpine

I get the following error:

npm ERR! notsup Unsupported engine for node-rdkafka@2.7.1: wanted: {"node":">=12.0.0"} (current: {"node":"10.13.0","npm":"6.4.1"})
npm ERR! notsup Not compatible with your version of node/npm: node-rdkafka@2.7.1
npm ERR! notsup Not compatible with your version of node/npm: node-rdkafka@2.7.1
npm ERR! notsup Required: {"node":">=12.0.0"}
npm ERR! notsup Actual:   {"npm":"6.4.1","node":"10.13.0"}

Any ideas about this inconsistency?

I clearly dont need a node version this high. But it says I do.

are you sure that it is working correctly on your local environment (the one with nvm) from the logs you could expect that there were probably some breaking changes that should not be allowed, if anything it's not an issue with docker but with your local node install that tricks the library to ignore node version — Krzysztof Krzeszewski, Sep 13 '19 at 13:52
the weird thing is that the minimal setup (simple docker file with `FROM node:10.13.0 RUN npm install node-rdkafka@2.7.1`) builds correctly for me, granted i don't use alpine because rdkafka required python executable and some other stuff i don't want to deal with settting up... could you provide entire `package.json` and `Dockerfile` ? — Krzysztof Krzeszewski, Sep 13 '19 at 14:02
FYI it was because there was a setting `engine-strict=true` in `.npmrc` file — Greg Peckory, Sep 13 '19 at 15:43

score 14 · Answer 1 · answered Sep 13 '19 at 16:31

14

Try to remove package-lock.json before npm install in Docker

rm package-lock.json
npm i

answered Sep 13 '19 at 16:31

Andrew

693
3
5

34

That doesn't fix it for me. – Linas Feb 06 '21 at 16:14
3

It also defeats the purpose of `package-lock.json`. – David Knipe Apr 04 '23 at 08:24

score 9 · Answer 2 · answered May 10 '21 at 08:50

The engines property in the package.json allows us to establish a range of versions.

With >=12 is asking for a node with version 12 or greater.

Therefore, the solution would be to install the requested version:

FROM node:12

Anyway, I recommend reviewing the versions supported by Docker currently here.

Unsupported engine node / NPM only when building in Docker

2 Answers2

Linked