Rancher Release - v1.6.3

Release v1.6.3


Supported Docker Versions

  • Docker 1.10.3
  • Docker 1.12.3-1.12.6
  • Docker 1.13.1 (Not supported with Kubernetes as Kubernetes does not support it yet)
  • Docker 17.03.0-ce (Not supported with Kubernetes as Kubernetes does not support it yet)
  • Docker 17.03.0-ee (Not with Kubernetes as Kubernetes does not support it yet)
  • Docker 17.06.0-ce (Not supported with Kubernetes as Kubernetes does not support it yet)
  • Docker 17.06.0-ee (Not with Kubernetes as Kubernetes does not support it yet)

Rancher Server Tags

Rancher server has 2 different tags. For each major release tag, we will provide documentation for the specific version.

  • rancher/server:latest tag will be our latest development builds. These builds will have been validated through our CI automation framework. These releases are not meant for deployment in production.
  • rancher/server:stable tag will be our latest stable release builds. This tag is the version that we recommend for production.

Please do not the releases with a rc{n} suffix. These rc builds are meant for the Rancher team to test out builds.

Beta - v1.6.3 - rancher/server:latest

Stable - v1.6.2 - rancher/server:stable

Important - Upgrade

  • In this release, we will automatically upgrade the network-services infrastructure stack as without this upgrade, your release will not work.
    • Upgrading from versions prior to Rancher v1.5.0 will trigger an automatic upgrade.
    • Upgrading from versions Rancher v1.5.0+ will not trigger an automatic upgrade.
  • In this release, if you make any changes to the default Rancher library setting for your catalogs and then roll back, you will need to reset the branch used for the default Rancher library under Admin -> Settings -> Catalog.


  • Kubernetes 1.6.6 [#7706, #8717]

    • Ability to integrate Rancher’s authentication with Kubernetes RBAC policies. By default, RBAC is turned off in the template and will need to be enabled. Read more about how to use RBAC in k8s. [#8717]
    • Updated to recommended default admission controllers [#8287]
    • Able to disable Rancher ingress controller [#8720]
    • By default, we now run daemon sets on hosts dedicated to Kubernetes orchestration components and etcd [#8397]
  • Ability to disable concurrent sessions for users [#8024] - By default, users can have concurrent sessions open. With this new enhancement, you can disable the ability to have concurrent sessions for users.

  • [CLI] Ability to add in environment variables for rancher run [#8589] - Thanks @jakubknejzlik!

Known Major Issues

  • Kubernetes 1.6 does not work with the native Docker version (v1.12.6) installed on RHEL. If you are running RHEL, please download upstream Docker version (v1.12.6). A fix will be made with Kubernetes 1.7, which will be released at end of July. [#9304]
  • If you are running Rancher without internet access or behind a proxy, catalog-service will panic and you will be logged out and unable to log in and default environment templates may not be present. #9378]

Major Bug Fixes since v1.6.2

  • Fixed an issue where Rancher server would get stuck in regex validation for images and drive up CPU [#7641]
  • Fixed an issue where metadata was not being updated correctly during upgrades with start before stop and the new container errored out [#8684]
  • Fixed an issue where setups using vxlan with hosts running 17.03+ were unable to communicate [#8635]
  • Fixed an issue where service FQDN was not being set correctly when using custom naming templates [#8641]
  • Fixed an issue where mapping 2 host ports to the same container port was not working [#8761]
  • Fixed an issue where load balancers would not work if a certificate name had a space [#8957]
  • Fixed an issue where you were unable to edit the service alias in the UI [#8959]
  • Fixed an issue where in Chinese mode you could not open the container shell [#8963]
  • Fixed an issue where a host with the scheduler was unable to schedule services when it couldn’t talk to metadata/dns [#9047]
  • Fixed an issue where load balancer ports were not showing up in metadata when a new port rule was added [#9172]

Rancher CLI Downloads

Rancher-Compose Downloads