Docker image with Ruby and Node.js with Yarn installed.
Based on the official Ruby image. Node and Yarn will be installed on top using the same approach from their official images.
Maintained combinations:
| Ruby | Node | Yarn | Status |
|---|---|---|---|
2.7.x |
14.x,16.x |
>=1.22 |
normal maintenance |
2.7.x |
15.x |
>=1.22 |
Node 15.x EOL: 2021-06-01 |
2.7.x |
13.x |
>=1.22 |
Node 13.x EOL: 2020-06-01 |
2.7.x |
12.x |
>=1.22 |
Node 12.x EOL: 2022-04-30 |
2.7.x |
11.x |
>=1.22 |
Node 11.x EOL: 2019-06-01 |
2.7.x |
10.x |
>=1.22 |
Node 10.x EOL: 2021-04-30 |
2.7.x |
9.x |
>=1.22 |
Node 9.x EOL: 2018-06-30 |
2.7.x |
8.x |
>=1.22 |
Node 8.x EOL: 2019-12-31 |
2.6.x |
8.x |
>=1.22 |
Ruby 2.6x EOL: 2022-03-31 |
2.5.x |
8.x |
>=1.19 |
Ruby 2.5x EOL: 2021-03-31 |
Note: More current versions of Ruby and Node will be added later.
Some applications, like Rails with Webpacker, requires both Ruby and Node.js to be installed in the same image in order to run or fully function.
There will be multiple variants of the tag versions to assist with selecting a specific docker image, depending on the needs of your application.
The Ruby, Node, and Yarn dependencies will be separated by a - and will be used in the following order: RUBY-NODE-YARN
An example of using Ruby 2.7.7, with Node 16.17.0 and Yarn 1.22.19 would be: 2.7.7-16.17.0-1.22.19
The bbdinc/ruby-node-yarn images come in following flavors:
debian (buster)
Note: alpine,stretch and slim might come later.
- Update the specific Dockerfile with required dependency updates.
- Update the README's Supported tags and any other documentation required.
- Commit locally as one commit and indicate which versions have changed in the commit message
- Build the Docker changes locally and tag it the same way as you want it on docker but exclude the organization.
docker build -f 2.7-16/buster/Dockerfile -t ruby-node-yarn:2.7.7-16.17.0-1.22.19 . - Tag the commit with the same Docker tag that is being added (don't push yet)
git tag 2.7.7-16.17.0-1.22.19 - If the build succeeds, then push your local Git repo with the pending commit/tag to the remote master branch
git push --tags origin master - Then list the local docker images to get the docker image id and perform a docker tag using the Image ID and include the Organization this time.
docker images REPOSITORY TAG IMAGE ID ruby-node-yarn 2.7.7-16.17.0-1.22.19 64557613a7f4 docker tag 64557613a7f4 benefitsbydesign/ruby-node-yarn:2.7.7-16.17.0-1.22.19 docker tag 64557613a7f4 benefitsbydesign/ruby-node-yarn:latest docker tag 64557613a7f4 bbdinc/ruby-node-yarn:2.7.7-16.17.0-1.22.19 docker tag 64557613a7f4 bbdinc/ruby-node-yarn:latest - Final step, is to push the Docker tags to Dockerhub. Reminder, ensure you are logged into Dockerhub hub locally before attempting to push using docker login
docker push benefitsbydesign/ruby-node-yarn:2.7.7-16.17.0-1.22.19 docker push benefitsbydesign/ruby-node-yarn:latest docker push bbdinc/ruby-node-yarn:2.7.7-16.17.0-1.22.19 docker push bbdinc/ruby-node-yarn:latest