jruby pulls statistics

Quick reference

• Maintained by: the Docker Community • Where to get help: the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow

Supported tags and respective Dockerfile links

• latest, 10, 10.1, 10.1.2, 10.1-jre, 10.1-jre21, 10.1.2-jre, 10.1.2-jre21, 10.1.2.0, 10.1.2.0-jre, 10.1.2.0-jre21 • 10-jdk, 10-jdk21, 10.1-jdk, 10.1-jdk21, 10.1.2-jdk, 10.1.2-jdk21, 10.1.2.0-jdk, 10.1.2.0-jdk21 • 10.1-jre25, 10.1.2-jre25, 10.1.2.0-jre25 • 10.1-jdk25, 10.1.2-jdk25, 10.1.2.0-jdk25 • 10.0, 10.0.7, 10.0-jre, 10.0-jre21, 10.0.7-jre, 10.0.7-jre21, 10.0.7.0, 10.0.7.0-jre, 10.0.7.0-jre21 • 10.0-jdk, 10.0-jdk21, 10.0.7-jdk, 10.0.7-jdk21, 10.0.7.0-jdk, 10.0.7.0-jdk21 • 10.0-jre25, 10.0.7-jre25, 10.0.7.0-jre25 • 10.0-jdk25, 10.0.7-jdk25, 10.0.7.0-jdk25 • 9, 9.4, 9.4.15, 9.4-jre, 9.4-jre8, 9.4.15-jre, 9.4.15-jre8, 9.4.15.0, 9.4.15.0-jre, 9.4.15.0-jre8 • 9-jdk, 9-jdk8, 9.4-jdk, 9.4-jdk8, 9.4.15-jdk, 9.4.15-jdk8, 9.4.15.0-jdk, 9.4.15.0-jdk8 • 9.4-jre11, 9.4.15-jre11, 9.4.15.0-jre11 • 9.4-jdk11, 9.4.15-jdk11, 9.4.15.0-jdk11 • 9.4-jdk17, 9.4.15-jdk17, 9.4.15.0-jdk17 • 9.4-jre17, 9.4.15-jre17, 9.4.15.0-jre17 • 9.4-jdk21, 9.4.15-jdk21, 9.4.15.0-jdk21 • 9.4-jre21, 9.4.15-jre21, 9.4.15.0-jre21 • 9.4-jdk25, 9.4.15-jdk25, 9.4.15.0-jdk25 • 9.4-jre25, 9.4.15-jre25, 9.4.15.0-jre25 • 9.3, 9.3.15, 9.3-jre, 9.3-jre8, 9.3.15-jre, 9.3.15-jre8, 9.3.15.0, 9.3.15.0-jre, 9.3.15.0-jre8 • 9.3-jdk, 9.3-jdk8, 9.3.15-jdk, 9.3.15-jdk8, 9.3.15.0-jdk, 9.3.15.0-jdk8 • 9.3-jre11, 9.3.15-jre11, 9.3.15.0-jre11 • 9.3-jdk11, 9.3.15-jdk11, 9.3.15.0-jdk11 • 9.3-jdk17, 9.3.15-jdk17, 9.3.15.0-jdk17 • 9.3-jre17, 9.3.15-jre17, 9.3.15.0-jre17 • 9.3-jdk21, 9.3.15-jdk21, 9.3.15.0-jdk21 • 9.3-jre21, 9.3.15-jre21, 9.3.15.0-jre21 • 10.0-dev-jre21 • 10.0-dev-jdk21 • 10.0-dev-jre25 • 10.0-dev-jdk25 • 10.1-dev-jre21 • 10.1-dev-jdk21 • 10.1-dev-jre25 • 10.1-dev-jdk25 • 9.4-dev-jre8 • 9.4-dev-jdk8 • 9.4-dev-jre11 • 9.4-dev-jdk11 • 9.4-dev-jdk17 • 9.4-dev-jre17 • 9.4-dev-jdk21 • 9.4-dev-jre21 • 9.4-dev-jdk25 • 9.4-dev-jre25

Quick reference (cont.)

• Where to file issues: https://github.com/jruby/docker-jruby/issues • Supported architectures: (more info) amd64, arm64v8 • Published image artifact details: repo-info repo's repos/jruby/ directory (history) (image metadata, transfer size, etc) • Image updates: official-images repo's library/jruby label official-images repo's library/jruby file (history) • Source of this description: docs repo's jruby/ directory (history)

What is JRuby?

JRuby (http://www.jruby.org) is an implementation of Ruby (http://www.ruby-lang.org) on the JVM.

Ruby is a dynamic, reflective, object-oriented, general-purpose, open-source programming language. According to its authors, Ruby was influenced by Perl, Smalltalk, Eiffel, Ada, and Lisp. It supports multiple programming paradigms, including functional, object-oriented, and imperative. It also has a dynamic type system and automatic memory management.

wikipedia.org/wiki/Ruby_(programming_language)

JRuby leverages the robustness and speed of the JVM while providing the same Ruby that you already know and love. With JRuby you are able to take advantage of real native threads, enhanced garbage collection, and even import and use java libraries.

How to use this image

Create a Dockerfile in your Ruby app project

Put this file in the root of your app, next to the Gemfile.

You can then build and run the Ruby image:

Generate a Gemfile.lock

The above example Dockerfile expects a Gemfile.lock in your app directory. This docker run will help you generate one. Run it in the root of your app, next to the Gemfile:

Run a single Ruby script

For many simple, single file projects, you may find it inconvenient to write a complete Dockerfile. In such cases, you can run a Ruby script by using the Ruby Docker image directly:

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's jruby/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Description from the Docker Hub listing.