Bug 1493147

Summary: docker-ce v17.07 is available
Product: [Fedora] Fedora Reporter: tn
Component: moby-engineAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: adimania, admiller, amurdaca, andreas.bierfert, bbaude, Bert.Deknuydt, carl, code, dwalsh, fedora, fedora, fkluknav, ichavero, imgx64+bzrh, jcajka, jchaloup, lsm5, miminar, nalin, ngompa13, paulo.fidalgo.pt, tim, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 18.06.0-2.ce.git0ffa825 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-27 16:16:43 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:

Description tn 2017-09-19 13:23:51 UTC
Latest upstream release: 17.07
Current version/release in rawhide: 1.13.1-31.git790e958.fc28
URL: https://github.com/docker/docker-ce/releases/tag/v17.07.0-ce

Notice that the GH docker/docker repository now redirects to moby/moby. The new target is docker/docker-ce.

Note: 17.09 rc2: https://github.com/docker/docker-ce/releases/tag/v17.09.0-ce-rc2

Related bug for docker-latest: https://bugzilla.redhat.com/show_bug.cgi?id=1492331

Comment 1 Olivier Samyn 2017-12-15 09:11:14 UTC
Docker-ce 17.09 is now available (and 17.12 in release candidate).

There is also some confusion between this package and docker-latest (which it at  an older version of docker)

Is there anything that blocks the docker update on fedora workstation and fedora server ? 

I understand there are maybe some incompatibilities with project atomic, but then is there something that prevent the docker-latest package to be updated ?

Can we help in some ways ?

Comment 2 Fedora End Of Life 2018-02-20 15:32:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.