-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
quay.io/podman tags don't match included podman version #5357
Comments
@TomSweeneyRedHat I think you maintain this image? |
Yes. Unfortunately when we tag a new Podman release quay.io automatically builds a "stable" version with that release number as a tag. However, the new release hasn't been made into an rpm yet, never mind getting it through the stable release platform. So I need to remove them "by hand" and then create the image once it reaches stable. I'll clean that up in the next day or two. |
FWIW, I've removed the badly labled tags from that repo. Podman v1.8 is not yet in stable and our first test sadly pointed to a packaging problem that we'll need to tend to. I also tried to build a v1.7 variant, but found issues with that RPM. Will post later versions once they become stable. |
It looks like 1.8.0 is available via
|
A friendly reminder that this issue had no activity for 30 days. |
Should be availabel now. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The podman images on
quay.io
have tags that don't match the version that's in the image.Steps to reproduce the issue:
Tag v1.6.2 has v1.6.2 in it:
But tag v1.6.5 has v1.6.2 in it (O_o):
Similarly for v1.8.1-rc2:
Describe the results you received:
The podman versions don't match the image tag.
Describe the results you expected:
The version of podman in an image should match the tag of the image.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:See above.
Output of
podman info --debug
:n/a
Package info (e.g. output of
rpm -q podman
orapt list podman
):n/a
Additional environment details (AWS, VirtualBox, physical, etc.):
n/a
The text was updated successfully, but these errors were encountered: