This image is officially deprecated in favor of the
node image. Please adjust your usage accordingly!
See iojs.org for more information, specifically the following note:
io.js has merged with the Node.js project again.
There won't be any further io.js releases. All of the features in io.js are available in Node.js v4 and above.
Supported tags and respective
For more information about this image and its history, please see the relevant manifest file (
library/iojs). This image is updated via pull requests to the
docker-library/official-images GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the
repos/iojs/tag-details.md file in the
docker-library/repo-info GitHub repo.
What is io.js?
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.
How to use this image
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
$ docker run -v "$PWD":/usr/src/app -w /usr/src/app -it --rm iojs iojs index.js
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 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.
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
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
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-
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.
Supported Docker versions
This image is officially supported on Docker version 17.03.1-ce.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a
cve-tracker issue on the
official-images repository first.
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.
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
README.md file before attempting a pull request.