You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the latest tag currently points to the same version as 3.2.2-jammy. However, I was expecting it to point to 3.3.0-jammy. Is this intentional?
If so, could you please clarify the policy regarding the latest tag?
If this is not intentional, could you kindly correct the version that the latest tag points to?
It's not intentional. I take-over maintainer of this repository and build/publish images. I only build 3.3.0-jammy and publish it. I work in progress to make that process automatically.
I tagged 3.3.0-jammy to latest now. Can you check it?
$ docker run -it rubylang/ruby:latest bash
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
root@356b291888e5:/# ruby -v
ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux]
root@356b291888e5:/# cat /etc/issue
Ubuntu 22.04.3 LTS \n \l
I was curious, but latest and 3.3.0-jammy have the same image id but are treated as different.
Activity
hsbt commentedon Jan 31, 2024
Thanks for your notice.
It's not intentional. I take-over maintainer of this repository and build/publish images. I only build
3.3.0-jammyand publish it. I work in progress to make that process automatically.I tagged
3.3.0-jammytolatestnow. Can you check it?akinomaeni commentedon Feb 1, 2024
Thank you!
I confirmed the image with the latest tag.
I was curious, but
latestand3.3.0-jammyhave the same image id but are treated as different.https://github.com/ruby/ruby-docker-images/pkgs/container/ruby/versions
