philipssoftware/node repository overview

⁠Docker images

This repo will contain docker images with node

Current versions available:

.
├── 14
│   ├── java
│   └── vanilla
├── 16
│   ├── java
│   ├── vanilla
│   └── yarn2
├── 18 -> lts / stable / active / latest
│   ├── java
│   ├── nixos
│   ├── vanilla
│   └── yarn2
├── 19 -> current
│   ├── java
│   ├── vanilla
│   └── yarn2

⁠Usage

Images can be found on https://hub.docker.com/r/philipssoftware/node/⁠.

docker run philipssoftware/node:lts node --version
docker run philipssoftware/node:14-java node --version && java -version

⁠Content

The images obviously contain nodeJS, but also two other files:

• REPO
• TAGS

⁠REPO

This file has a url to the REPO with specific commit-sha of the build. Example:

$ docker run philipssoftware/node:14 cat REPO
https://github.com/philips-software/docker-node/tree/facb2271e5a563e5d6f65ca3f475cefac37b8b6c

⁠TAGS

This contains all the similar tags at the point of creation.

$ docker run philipssoftware/node:14 cat TAGS
node node:stable node:14 node:14.21.3 node:14.21.3 node:14.21.3-stretch

You can use this to pin down a version of the container from an existing development build for production. When using node:11 for development. This ensures that you've got all security updates in your build. If you want to pin the version of your image down for production, you can use this file inside of the container to look for the most specific tag, the last one.

⁠Node and Java version

If you want to know the version of Node (or Java if available), you can do the following:

$ docker run -it philipssoftware/node:18

⁠Simple Tags

Tags are aligned with the Node release schedule⁠.

⁠nodeJS 18 lts / stable

• node:stable node:latest node:lts``node:18 node:18.15 node:18.15.0 node:18.15.0-buster stable/vanilla/Dockerfile⁠

⁠nodeJS 19 current

• node:current node:19 node:19.8 node:19.8.1 node:19.8.1-buster current/vanilla/Dockerfile⁠

⁠nodeJS 16 - not recommended (use stable or lts)

• node:16 node:16.19 node:16.19.1 node:16.19.1-buster 16/vanilla/Dockerfile⁠

⁠nodeJS 14 - not recommended (use stable or lts)

• node:14 node:14.21 node:14.21.3 node:14.21.3-buster-slim 14/vanilla/Dockerfile⁠

⁠Tags with yarn2

⁠nodeJS 18 lts / stable - Yarn 2

• node:yarn2 node:latest-yarn2 node:stable-yarn2 node:lts-yarn2 node:18-yarn2 node:18.15-yarn2 node:18.15.0-yarn2 node:18.15.0-buster-yarn2 stable/yarn2/Dockerfile⁠

⁠nodeJS 19 current - Yarn 2

• node:current-yarn2 node:19-yarn2 node:19.8-yarn2 node:19.8.1-yarn2 node:19.8.1-buster-yarn2 current/yarn2/Dockerfile⁠

⁠nodeJS 16 Yarn 2

• node:16-yarn2 node:16.19-yarn2 node:16.19.1-yarn2 node:16.19.1-buster-yarn2 16/yarn2/Dockerfile⁠

⁠Tags with openjdk

⁠nodeJS 18 lts / stable - java

• node:java node:latest-java node:stable-java node:lts-java node:18-java node:18.15-java node:18.15.0-java node:18.15.0-buster-java stable/java/Dockerfile⁠

⁠nodeJS 19 current - java

• node:current-java node:19-java node:19.8-java node:19.8.1-java node:19.8.1-buster-java current/java/Dockerfile⁠

⁠nodeJS 16 java

• node:16-java node:16.19-java node:16.19.1-java node:16.19.1-buster-java 16/java/Dockerfile⁠

⁠Why

We often need some tools in a container for checking some things. F.e. jq⁠, aws-cli⁠ and curl⁠. We can install this every time we need a container, but having this baked into a container seems a better approach.

That's why we want our own docker file definitions.

⁠Issues

• If you have an issue: report it on the issue tracker⁠

⁠Author

• Jeroen Knoops [email protected]⁠
• Niek Palm [email protected]⁠

⁠License

License is MIT. See LICENSE file⁠

⁠Philips Forest

This module is part of the Philips Forest.

                                                     ___                   _
                                                    / __\__  _ __ ___  ___| |_
                                                   / _\/ _ \| '__/ _ \/ __| __|
                                                  / / | (_) | | |  __/\__ \ |_
                                                  \/   \___/|_|  \___||___/\__|

                                                                 Infrastructure

Talk to the forestkeepers in the docker-images-channel on Slack.