Bug 1131197

Summary: [RFE] Update Docker to 1.1
Product: Red Hat Enterprise Linux 7 Reporter: Eric Rich <erich>
Component: dockerAssignee: Daniel Walsh <dwalsh>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: bsarathy, dswegen, dwalsh, garret.taylor, jherrman, jyundt, mjenner, rmarigny, sghosh
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
The docker package has been upgraded to upstream version 1.1.2, which provides a number of bug fixes and enhancements over the previous version.
Story Points: ---
Clone Of:
: 1139696 (view as bug list) Environment:
Last Closed: 2014-09-18 20:46:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1064025, 1109938, 1139696    

Description Eric Rich 2014-08-18 16:21:31 UTC
Description of problem:

Would like to see docker updated to version 1.1

Comment 3 Daniel Walsh 2014-08-21 12:38:35 UTC
We are releasing docker 1.1.2 into HTB2 next week, and then it will go to customers two weeks later.

Comment 6 Daniel Walsh 2014-08-30 10:29:05 UTC
We are releaseing docker-1.1-2 which has lots of the updates in docker-1.2.  Please check to see if this satisfies their needs.  

We will start testing and working with docker-1.2 this week.

Comment 7 David Swegen 2014-09-11 11:48:31 UTC
Is there a list anywhere of patches that will be backported from 1.2 to 1.1?

Comment 8 Daniel Walsh 2014-09-11 13:35:46 UTC
We went back to just shipping docker 1.1.2 base with only a patch for RHEL Secrets.  It should be shipping soon.

We are also working on a docker 1.2 which will be in HTB3.

Comment 11 errata-xmlrpc 2014-09-18 20:46:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1266.html