[openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Steven Dake (stdake) stdake at cisco.com
Wed May 17 16:00:00 UTC 2017


When a docker image is pushed to dockerhub (or quay.io, etc) a tag is specified.  If the tag already exists, it is overwritten.


-----Original Message-----
From: Doug Hellmann <doug at doughellmann.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Wednesday, May 17, 2017 at 8:55 AM
To: openstack-dev <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev]	[tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes]	do we want to be publishing binary container images?

    Excerpts from Chris Dent's message of 2017-05-17 12:14:40 +0100:
    > On Wed, 17 May 2017, Thierry Carrez wrote:
    > > Back to container image world, if we refresh those images daily and they
    > > are not versioned or archived (basically you can only use the latest and
    > > can't really access past dailies), I think we'd be in a similar situation ?
    > Yes, this.
    Is that how container publishing works? Can we overwrite an existing
    archive, so that there is only ever 1 version of a published container
    at any given time?
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list