Minimal Node.js Docker Images built on Alpine Linux with support for DNS service discovery
A port of janeczku/alpine-kubernetes to use mhart/alpine-node as its base image to provide DNS support for micro-services containers in Kubernetes, Console, Docker Cloud or other Docker cluster environments that use DNS-based service discovery and rely on the containers being able to use the search domains from resolv.conf for resolving service names. Versions built on Alpine Linux.
- Full install built with npm:
8.13.08.138latest8.9.48.988.9.08.986.2.16.266.1.06.16.0.06.05.12.05.1255.11.15.115.11.05.10.15.1055.10.04.4.74.444.4.44.4.34.4.24.4.14.4.04.3.24.34.3.14.3.00.12.150.1200.12.140.12.130.12.120.12.11
- Base install built as static binary without npm:
base-8.13.0base-8.13base-8base-latestbase-8.9.4base-8.9base-8base-8.9.0base-8.9base-8base-6.1.0base-6.1base-6base-6.0.0base-6.0base-5.11.1base-5.11base-5base-5.11.0base-5.10.1base-5.10base-5base-5.10.0base-4.4.4base-4.4base-4base-4.4.3base-4.4.2base-4.4.1base-4.4.0base-4.3.2base-4.3base-4.3.1base-4.3.0base-0.12.14base-0.12base-0base-0.12.13base-0.12.12base-0.12.11
$ docker run quay.io/trunk/alpine-node-kubernetes node --version
v8.9.4
$ docker run quay.io/trunk/alpine-node-kubernetes node --version
v6.1.0
$ docker run quay.io/trunk/alpine-node-kubernetes:5 node --version
v5.1.0
$ docker run quay.io/trunk/alpine-node-kubernetes:4 node --version
v4.4.4
$ docker run quay.io/trunk/alpine-node-kubernetes npm --version
v3.4.0
$ docker run quay.io/trunk/alpine-node-kubernetes:base node --version
v6.1.0
If you don't have any native dependencies, ie only depend on pure-JS npm
modules, then my suggestion is to run npm install locally before running
docker build (and make sure node_modules isn't in your .dockerignore) –
then you don't need an npm install step in your Dockerfile and you don't need
npm installed in your Docker image – so you can use one of the smaller
base* images.
It is recommended you setup you process to run using s6
as s6 is using ENTRYPOINT to run its init. Example usage can be found in
janeczku/alpine-kubernetes.
FROM quay.io/trunk/alpine-node-kubernetes:base
# FROM quay.io/trunk/alpine-node-kubernetes:base-0.10
# FROM quay.io/trunk/alpine-node-kubernetes
WORKDIR /src
# Copy the s6 service.d file(s)
# S6 requires and executable (755) runfile to be deployed to:
# /etc/services.d/{APPLICATION NAME}/run
COPY rootfs /
# Copy the application
COPY bin ./bin
# If you have native dependencies, you'll need extra tools
# RUN apk add --update make gcc g++ python
# If you need npm, don't use a base tag
# RUN npm install
# If you had native dependencies you can now remove build tools
# RUN apk del make gcc g++ python && \
# rm -rf /tmp/* /var/cache/apk/* /root/.npm /root/.node-gyp
EXPOSE 3000
# If you don't want to use s6, you must use CMD
# CMD ["node", ".bin/index.js"]
./upgrade 6.1.0 4.4.4
git push --tags -f
Run ./upgrade [version...] to produce new Dockerfiles tagged with the given versions
with and without npm.
This will also manage upgrading partial versions. When the given version is the newest
for the partial it will replace the previous version, including latest.
Pushing to master will result in all new tags being built in quay.io.
As Alpine Linux uses musl, you may run into some issues with environments expecting glibc-like behaviour (for example, Kubernetes). Some of these issues are documented here:
Inspired by: