[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: registry.access.redhat.com/openshift3/ose:latest wrongly tagged?



For the official OpenShift Container Platform (OCP) images, you should
*not* use "latest"

The definition of "latest" for docker images is "The last image pushed
into the registry with that name."

As Jonathan showed, there are alot of images for openshift3/ose, and
all sorts of different versions.  OCP is the enterprise version of
Origin.  Because of that, we still support the older versions, and we
have updates for those older versions.
Because we have updates for those older versions, the "latest" tag,
gets changed quite a bit, and goes to all different types of versions.

What should you use if you want the latest 3.5 image?
openshift3/ose:v3.5

The v<version> tag is the latest image for that version.
So if you want the latest 3.4 image, you get openshift3/ose:v3.4 for
3.3 get openshift3/ose:v3.3 and so forth.

Is this documented?
Documentation is currently being updated and we should have a URL for
you in a week or two with better explanation than this.  We apologize
that this wasn't documented before.

On a different note, since the registry handles both v1 and v2
registry commands, you can query the registry with curl to get the
listings, along with the image sha sum.  I like this way because I can
then see which tags go with which image.

$ curl -k http://registry.access.redhat.com/v1/repositories/openshift3/ose/tags
| python -m json.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8798  100  8798    0     0  47409      0 --:--:-- --:--:-- --:--:-- 47556
{
    "latest": "38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
    "v3.1": "241393b078ca6bfe9f83bad824bd41692eecc6fd2d641b9f7ba34df319bd2536",
    "v3.1.0.4":
"62208f15133798af253a651386ae2753da9130fcc68f1863cbd735c547356173",
    "v3.1.0.4-1":
"2eb816e9a7d05f6d5816be42ba21cf272770a9be1d15e839e7474c0541a40bc7",
...
    "v3.4.1.7":
"c729d138d383fb273a520341e5671b4e2fcd2ad77c062b6e9ad725fd06af33ff",
    "v3.4.1.7-2":
"c729d138d383fb273a520341e5671b4e2fcd2ad77c062b6e9ad725fd06af33ff",
    "v3.5": "38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
    "v3.5.5.5":
"ace03132c45fd6c32233f5b588db2812e341cadf46a4b2a9298699c64f0f81ac",
    "v3.5.5.5-2":
"ace03132c45fd6c32233f5b588db2812e341cadf46a4b2a9298699c64f0f81ac",
    "v3.5.5.8":
"38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3",
    "v3.5.5.8-3":
"38d0523d03b7c155031f20ff54c47836bef577bc1c3392de9cfcc549b0da77d3"
}

You'll notice that right now, "latest" is actually pointing to the
latest 3.5 image.  But that is only because the 3.5 image was the last
image pushed up to the registry.

I hope this helps.  Like I said, documentation is coming.  I'm sorry
it wasn't up before now.

Troy



On Tue, May 9, 2017 at 11:56 AM, David Schweikert <david schweikert ch> wrote:
> Hi Jonathan,
>
> On Tue, May 09, 2017 at 09:36:48 -0700, Jonathan Yu wrote:
>> I've confirmed the problem using the skopeo tool and am asking around
>> about a resolution. The build date looks pretty recent, so it's
>> possible that the old version was rebuilt and therefore ended up as
>> the "latest" - give us some time to investigate & we'll provide an
>> update here.
>
> OK, thanks for the very quick reaction!
>
> Also, thanks for the hint about the skopeo tool. Looks very useful.
>
> Cheers
> David
>
> _______________________________________________
> users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]