Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Regarding the latest Tag #60

Open
akinomaeni opened this issue Jan 30, 2024 · 2 comments
Open

Query Regarding the latest Tag #60

akinomaeni opened this issue Jan 30, 2024 · 2 comments

Comments

@akinomaeni
Copy link
Contributor

I appreciate your daily maintenance efforts.

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?

Refs

@hsbt
Copy link
Member

hsbt commented 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-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?

@akinomaeni
Copy link
Contributor Author

Thank you!

I confirmed the image with the latest tag.

$ 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.

https://github.com/ruby/ruby-docker-images/pkgs/container/ruby/versions
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants