Docker image with Ruby and Node.js with Yarn installed and ready to roll.
Both Ruby and Node.js are based on official images.
Maintaned combinations:
- Ruby: 2 (2.4) Node: 6 (6.10)
- Ruby: 2 (2.4) Node: 8 (8.0)
latest
,2-8
(2-6/Dockerfile)slim
,2-8-slim
(2-6/slim/Dockerfile)alpine
,2-8-alpine
(2-6/alpine/Dockerfile)2-6
(2-6/Dockerfile)2-6-slim
(2-6/slim/Dockerfile)2-6-alpine
(2-6/alpine/Dockerfile)2-4
(2-4/Dockerfile)2-4-slim
(2-4/slim/Dockerfile)2-4-alpine
(2-4/alpine/Dockerfile)
Some applications, like Jekyll, GitHub pages or Rails with Webpacker, requires both Ruby and Node.js installed in the same image in order to run or fully function.
$ docker run -v "$PWD":/usr/src/app -p "8080:8080" starefossen/ruby-node
The starefossen/ruby-node
images come in three flavors, each designed for a
specific use case.
starefossen/ruby-node:latest
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.
starefossen/ruby-node:slim
A slimmed down image, identical to the :latest
tag except it is based a Debian
base image with fewer packages and dependencies installed like without GCC and
various build tools.
starefossen/ruby-node:alpine
This is the smalles image possible. It is based on the Alpine Linux base image.
Versions 2-6, 2-8 (latest and slim) has defined locale C.UTF-8 instead default POSIX.
This Docker image is licensed under the MIT License.
Software contained in this image is licensed under the following:
- Ruby: GPLv2
- Node.js: MIT License
This image is officially supported on Docker version v17.
Support for older versions (down to v1.0) is provided on a best-effort basis.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
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.