Isn’t using both the “latest” and “stable” tags for the same release a contradiction?
rancher/server:latest tag … These releases are not meant for deployment in production.
rancher/server:stable tag … This tag is the version that we recommend for production.
I just upgraded from 1.1.3 to stable and I am experiencing #7523; am I now using a “stable” release or a development build?
latest is the newest release of the main line. stable is the release recommended for production (or more directly, what we support for customers). Both have gone through our QA.
There’s no reason they can’t be the same release, and they often are for 1.x.1 because we do a monthly release, see what comes up and then mark it stable a week or so later or do a .1 if needed.
ok; thank you for the clarification.
I cannot seem to pull the image keep getting manifest not found.
Getting Manifest for rancher/server:latest not found
Amazon S3 is currently down and taking most of the internet with it, including DockerHub.
Our current latest release is Rancher v1.5.0.
Our current latest and stable release is Rancher v1.5.2.
Our current latest and stable release is Rancher v1.5.4.
Our current and latest stable release is Rancher v1.5.5.
Our latest and stable release is Rancher v1.5.6.
Our latest and stable release is Rancher v1.5.7.
Our latest and stable release is Rancher v1.5.8.
Our current and latest release is Rancher v1.5.9
Our current latest release is Rancher v1.6.0.
Our current stable release is Rancher v1.5.9.
Our current latest release is Rancher v1.6.0.
Our current stable release is Rancher v1.5.10.
Our current latest release is Rancher v1.6.1.
Our current stable release is Rancher v1.5.10.
Our current latest and stable release is Rancher v1.6.2.
Hi Team,
are there any updates on v1.7?
End of may seems to be a bit outdated…
Thx
Andreas
Hi there,
The road map seems empty for a while, and I need to know when you gonna support the latest-stable docker community edition ?
Thanks a lot