Christopher Horrell
Christopher Horrell
Is this specific to v6.2.2? Also, is this something that could be done in your own Docker file that builds on top of the current image?
Yeah, that would be great. I think if we do that we'd have to somehow build node without npm. Or convince the build group that we need that as another...
Yeah they build node with `--without-npm`. We could probably do the same thing but the build and release would take longer.
Is this worth revisiting as a variant? Doing `rm -rf /usr/local/lib/node_modules/npm/ /usr/local/bin/npm` is easy enough and it would be useful with multi-stage builds. And what would we call the variant?
I think we should only do this for Debian, something like: ```Dockerfile FROM debian:jessie-slim RUN groupadd --gid 1000 node \ && useradd --uid 1000 --gid node --shell /bin/bash --create-home node...
Also, for a variant name, I kind of like `node:core`, `node:10-core` etc.
We're looking at a ~60MB difference using the `rm -r` approach: ```console [chorrell:~/GitHub/docker-node-main] master(+6/-6)* ± docker images | grep 10.2.0-slim node 10.2.0-slim c164ad185a38 20 hours ago 184MB ``` vs ```console...
Note that I don't think the statically compiled versions are available, or at least I cannot find them at `https://nodejs.org/dist/` for v10. And we would want versions for each of...
The output indicates that the image is multi-platform...unless you are looking for an architecture/os combination that we don't support?
Is this still pending another review?