docker-node

Official docker image for node is built from Alpine or Debian [1] Forgive me if I don't believe that running a full OS on a host OS to run a single node command doesn't amount to running a VM. [1] https://github.com/nodejs/docker-node/tree/main/20

Node is about 60mb on it's own. Taking a peak at the official dockerfile for alpine node (https://github.com/nodejs/docker-node/blob/28ad5e0e5d0e80df4...), they're also pulling in the following packages && apk add --no-cache --virtual .build-deps-full \ binutils-gold \ g++ \ gcc \ gnupg \ libgcc \ linux-headers \ make \ python3 My guess is the most weight is probably coming from linux-headers (~10mb), python3 (~50mb), and nodejs (~60mb). Plus 1 to 10 mb for each of the other pacakges, and you end up right there around 175mb.

Node.js has both a Best Practices [0] and a tutorial [1] that instruct to use CMD ["node", "main.js"]. In short: do not run NPM as main process; instead, run Node directly. This way, the Node process itself will run as PID 1 of the container (instead of just being a child process of NPM). The same can be found in other collections of best practices such as [2]. What I do is a bit more complex: an entrypoint.sh which ends up running exec node main.js "$*" Docs then tell users to use "docker run --init"; this flag will tell Docker to use the Tini minimal init system as PID 1, which handles system SIGnals appropriately. [0]: https://github.com/nodejs/docker-node/blob/main/docs/BestPra... [1]: https://nodejs.org/en/docs/guides/nodejs-docker-webapp/ [2]: https://dev.to/nodepractices/docker-best-practices-with-node... Edit: corrected the p

> There being no password also does not matter, as you are by default already running everything as root. Who cares if root can become root? Best practice would have you switch to a non root user before running whatever it is inside the container. Although if you haven’t added any suid binaries by accident then there’s no way to go back. E.g. the node alpine image adds a “node:node” user and group for the process to run as instead of root. https://github.com/nodejs/docker-node/blob/master/10/alpine/...

I was the one who added Yarn to the official docker-node image[1][2]. This was the most popular docker-node feature request at the time. We managed to achieve it with a minimal size increase (with the help of the awesome Yarn team) and without affecting anything else. There was already a history of us providing some bonus features which the upstream Node project doesn't, such as a musl-libc build (for Alpine Linux). [1] https://github.com/nodejs/docker-node/pull/337 [2] https://github.com/nodejs/docker-node/pull/403

Not quite the same but ironically the standard "node" Docker image contains yarn: https://github.com/nodejs/docker-node/blob/b502aa016335c81a5...