A simple docker image that supports building, testing and exporting the build content as a tar.
0.12
,0.12.18
, (Dockerfile)0.12-onbuild
,0.12.18-onbuild
, (Dockerfile.onbuild)0.12-onbuild-bower
,0.12.18-onbuild-bower
, (Dockerfile.onbuild-bower)4
,4.7
,4.7.2
, (Dockerfile)4-onbuild
,4.7-onbuild
,4.7.2-onbuild
, (Dockerfile.onbuild)4-onbuild-bower
,4.7-onbuild-bower
,4.7.2-onbuild-bower
, (Dockerfile.onbuild-bower)5
,5.12
,5.12.0
, (Dockerfile)5-onbuild
,5.12-onbuild
,5.12.0-onbuild
, (Dockerfile.onbuild)5-onbuild-bower
,5.12-onbuild-bower
,5.12.0-onbuild-bower
, (Dockerfile.onbuild-bower)6
,6.9
,6.9.4
,lts
, (Dockerfile)6-onbuild
,6.9-onbuild
,6.9.4-onbuild
,lts-onbuild
, (Dockerfile.onbuild)6-onbuild-bower
,6.9-onbuild-bower
,6.9.4-onbuild-bower
,lts-onbuild-bower
, (Dockerfile.onbuild-bower)7
,7.4
,7.4.0
,latest
, (Dockerfile)7-onbuild
,7.4-onbuild
,7.4.0-onbuild
,onbuild
, (Dockerfile.onbuild)7-onbuild-bower
,7.4-onbuild-bower
,7.4.0-onbuild-bower
,onbuild-bower
, (Dockerfile.onbuild-bower)
Create a Dockerfile in your Node.js app project
FROM umweltdk/node:0.12-onbuild
# replace this with your application's default port
EXPOSE 8888
Build an image for your app
$ docker build -t my-nodejs-app .
$ docker run -it --rm my-nodejs-app test
$ docker run -it --rm --name my-running-app my-nodejs-app
To export a tar of the built app directory:
$ docker run --rm my-nodejs-app slug - > app.tar.gz
Use this if you want to upload a site to something like S3.
The node
images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of node
but adds a user, so everything is not run as root and an entrypoint to support testing and export the build product.
This image makes building derivative images easier. For most use cases, creating a Dockerfile
in the base of your project directory with the line FROM node:onbuild
will be enough to create a stand-alone image for your project.
While the onbuild
variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over when the ONBUILD
triggers fire (see also docker/docker#5714
, docker/docker#8240
, docker/docker#11917
).
Once you've got a handle on how your project functions within Docker, you'll probably want to adjust your Dockerfile
to inherit from a non-onbuild
variant and copy the commands from the onbuild
variant Dockerfile
(moving the ONBUILD
lines to the end and removing the ONBUILD
keywords) into your own file so that you have tighter control over them and more transparency for yourself and others looking at your Dockerfile
as to what it does. This also makes it easier to add additional requirements as time goes on (such as installing more packages before performing the previously-ONBUILD
steps).
This image is very much like the onbuild variant except that it has an ONBUILD line for doing bower install
which means that the caching will be better when you use bower and you use this image.