1.8.1,1.8,1,latest(1.8/Dockerfile)1.8.1-onbuild,1.8-onbuild,1-onbuild,onbuild(1.8/onbuild/Dockerfile)1.8.1-slim,1.8-slim,1-slim,slim(1.8/slim/Dockerfile)
For more information about this image and its history, please see the relevant manifest file (library/iojs) in the docker-library/official-images GitHub repo.
io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
If you want to distribute your application on the docker registry, create a Dockerfile in the root of application directory:
FROM iojs:onbuild
# Expose the ports that your app uses. For example:
EXPOSE 8080
Then simply run:
$ docker build -t iojs-app
...
$ docker run --rm -it iojs-app
To run a single script, you can mount it in a volume under /usr/src/app. From the root of your application directory (assuming your script is named index.js):
$ docker run -v "$PWD":/usr/src/app -w /usr/src/app -it --rm iojs iojs index.js
The iojs 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 buildpack-deps. buildpack-deps is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
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 iojs:onbuild will be enough to create a stand-alone image for your project.
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run iojs. Unless you are working in an environment where only the iojs image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
View license information for the software contained in this image.
This image is officially supported on Docker version 1.6.0.
Support for older versions (down to 1.0) is provided on a best-effort basis.
Documentation for this image is stored in the iojs/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's REAMDE.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.