Rancher Compose CLI support for image force pull [#1955, #1094] - Rancher Compose CLI now supports new capabilities to update images on hosts.
rancher-compose pull- pulls the specified image on a service to all hosts that match the host affinity scheduling rule for that service. No scheduling rules means all hosts in the environment.
rancher-compose pull --cached- pulls the specified image on a service to all hosts that match the host affinity scheduling rule AND the image must already exist on that host. Again, no scheduling rules means all hosts in the environment. This is typically used to force update an existing image on the host due to Docker caching.
rancher-compose upgrade --pull- on rolling upgrade, specifying --pull will update the image first on the host before starting new containers.
io.rancher.container.pull_image: alwaysin a container or service will result in Rancher always force pulling the image before starting the container.
- Improved Rancher Server installation - With this release, Rancher Server will no longer require any internet access for installation.
- Improved monitoring stats for containers and hosts [#1265] - Added additional network and storage monitoring stats to hosts and containers. You will now also be able to view container stats in an aggregated view under hosts and services without requiring to click into each individual container.
Known Major Issues
- Unable to add EC2/Rackspace hosts using UI [#2104]
rancher-compose pullwith private registries is not pulling new images [#2107, #2110]
Major Bug Fixes since v0.37.0
- rancher-compose: Added support to create LB services with SSL enabled [#1929]
- rancher-compose: Fixed an issue where containers from the original service does not get properly removed during a rancher compose rolling upgrade if the service had the global scheduler label added.[#1878]
- rancher-compose: Added a “cleanup” flag for rolling upgrades that will remove the previous service after a successful upgrade [#1817]
- rancher-compose: Fixed an issue where have no links defined in a service will not properly remove the links for the existing service [#1717]
- rancher-compose: Added improved handling of invalid characters in stack/project names [#1565]
- rancher-compose: Fixed an issue here cpu_sets does not get properly added to the container run command [#1335]
- Fixed an issue where an inactive GitHub account was still capable of logging into Rancher [#2014]
- Fixed an issue where using a link with a sidekick results in a container that is stuck in a “Networking” state. [#2040]
- Fixed an issue where Rancher where resulting name created from specifying the
io.rancher.container.hostname_overrideflag is no longer larger than 64 chars and prevent the containers from starting. [#1934]