Closed loganhz closed 6 years ago
@cjellick @deniseschannon
We need a naming policy for the server base image.
For now, we will have two versions of server-base
, v1.6 and v2.0. I would suggest:
rancher/server-base:v1.6
and rancher/server-base:v2.0
will point to the latest build of the image for either version. (We will only deal with v1.6 in this commit)rancher/server-base:v1.6-<date>
and rancher/server-base:v1.6
. Then someone can manually push the image with both tags to the docker hub.As an alternative, we may tag the image as rancher/server-base:v1.6-<commit>-<date>
instead of rancher/server-base:v1.6-<date>
, but IMO this Dockerfile won't be changed often, so I think we can get away with date tag only.
my initial reaction is that we should not deviate from our simple semantic versioning that we currently use across the board. we only every do v
@cjellick @loganhz
OK, let's use version
script and tag to mark the release.
The first version will be v1.0.0
(git tagged so it will be picked by version script). The version script is available at e.g. https://github.com/rancher/agent/blob/master/scripts/version
@yasker updated
rancher/server-base:v1.0.0
was pushed.
@yasker Can you help to build and push as
rancher/server-base
, please ? Thanks a lot