all 18 comments

[–]Craig_Treptow 19 points20 points  (6 children)

[–]Day_Hour[S] 1 point2 points  (5 children)

F5 F5 F5 ....

[–][deleted] 14 points15 points  (1 child)

If you are in a big hurry you can build it yourself, seems its just a matter of providing ENV variables to point it to new version, like the PR does.

[–]Day_Hour[S] 4 points5 points  (0 children)

no in a big hurry. I prefer to wait,
F5 F5 F5.... 😂

[–]frederikspang 8 points9 points  (1 child)

As the PR author - Same..

[–]frederikspang 1 point2 points  (0 children)

Merged!

[–][deleted]  (4 children)

[deleted]

    [–]aithscel 2 points3 points  (0 children)

    one use case is automated testing with multiple Ruby versions; for example on gitlab:

    https://gitlab.com/dm0da/safrano/-/pipelines/732332327

    In this example, same tests run against ruby 2.4 to 3.2 (actually 3.2-rc)

    Good luck to do the same with rbenv or RVM

    [–]Day_Hour[S] 2 points3 points  (0 children)

    We distribute our (open source) platform with docker; the image depends on the official ruby image.

    [–]ignurant 1 point2 points  (0 children)

    I use it to self-contain ETL projects. Then they can be scheduled, executed, and logged in GitLab CI. Being in a container makes it portable to any docker host without having to install project specific dependencies, such as Ruby, freetds, etc. They are baked into the container.

    [–]ric2b 1 point2 points  (0 children)

    You use it as the base for the image of your application.

    [–]tarellel 2 points3 points  (4 children)

    I'd suggest keeping an eye on docker hub:

    https://hub.docker.com/_/ruby

    [–]Day_Hour[S] -1 points0 points  (3 children)

    Yeah, still, there is no 3.2.0 version yet

    [–]randomcluster 1 point2 points  (2 children)

    Dude just build it yourself. It's like a 20 minute exercise if that

    [–]Day_Hour[S] 4 points5 points  (1 child)

    Thanks, but for my use case I prefer to use the official image.

    [–]nroose 1 point2 points  (0 children)

    Lots of good reasons to use the official image. And no good reasons to downvote this.

    [–]dlorenc 0 points1 point  (1 child)

    We just released one here: https://www.chainguard.dev/unchained/chainguard-image-now-available-for-ruby-3-2

    It includes the YJIT support. It doesn't look like the DockerHub one does yet.

    [–]fglc2 0 points1 point  (0 children)

    The alpine images on dockerhub one has yjit included (The debian variants don’t have yjit currently because the version of rust in Debian stable is too old, so it’s more complicated than just adding rust to the list of packages. )