Building of Docker images based upon 8.0


#1

So, I’ve got a hell of an issue.

Right now, 8.0 just went GM. And we’ve been waiting for this work weeks in my team. This means we’ve got all our internal tooling setup for 8.0.

This includes our images.

The rub is that when we go to build our image for production, the node container fails a the install stage. A far as we can trace it has something to do with a package building native extensions.

Any one got any insight?


Getting a weird EINVAL error with npm on CircleCI 2.0
#2

Can you provide:

  • CircleCI version you are using
  • versions of any tools
  • any relevant Dockerfiles that you can share
  • as much of our config file as you’re willing to share
  • the exact error message/output you are getting
  • if it’s a public project, build URL, otherwise feel free to PM it to me

Thanks


#3

Circle CI Version 1.

Nothing beyond stock npm/node.

Sadly, I can’t share any of the images/configs.


#4

Same here. Getting these errors on npm install:

npm ERR! Cannot read property 'write' of null
npm ERR! Cannot read property 'write' of null
npm ERR! Cannot read property 'write' of null
npm ERR! Cannot read property 'write' of null
npm ERR! Cannot read property 'write' of null

btw, I’m using CircleCI 2.0, node v8, npm 5. You can check the failures here: https://circleci.com/gh/WisePricer/quadro/248


#5

Have either of you ran a build using npm@5 with “Rebuild without cache”? Any shrinkwrap files that you can delete before the build?


#6

Yes. Ran it without cache. Same result. Ran it also with a custom image. Same result


#7

The repo above is opensource - so you can play with it and see it failing


#8

I get this issue when updating npm to 5 regardless of the node version.


#9

Another thread on this. `npm install` error that isn’t reproducing in a local Docker container You can use Node 8 but you’ll need to use Yarn till Circle fixes the issue with NPM 5.


#11