I think we should get docker-1.13 into Rawhide right away. The problem with putting it into Fedora 25 is it has not been fully vetted with OpenShift and Kubernetes yet. I don't believe we should swap out the docker version their until OpenShift is ready.

Putting it into updates-testing and leaving it there until OpenShift says it is ready to consume it the best option. I think we should also create a system container for Fedora 25 with the docker-1.13 runtime in it which would allow Fedora Atomic Host users to consume it. We really need to start getting some play time with system containers, and this is probably the best time.

@gscrivano Has done some nice work on this, and it is time to get it exposed.

I think we should get docker-1.13 into Rawhide right away.

agree on this point. The discussion was meant to target f25.

I think we should get docker-1.13 into Rawhide right away. The problem with putting it into Fedora 25 is it has not been fully vetted with OpenShift and Kubernetes yet. I don't believe we should swap out the docker version their until OpenShift is ready.
Putting it into updates-testing and leaving it there until OpenShift says it is ready to consume it the best option. I think we should also create a system container for Fedora 25 with the docker-1.13 runtime in it which would allow Fedora Atomic Host users to consume it. We really need to start getting some play time with system containers, and this is probably the best time.
@gscrivano Has done some nice work on this, and it is time to get it exposed.

Any pointers to docker-1.13 in system container?

None have been created yet. I will attempt to get one built as soon as we have docker-1.13 in updates-testing.

-1 on docker 1.13 for now: https://twitter.com/jbeda/status/826969113801093121

Awesome.

I'm not a fan of updating docker within a distro release. Docker "minor" updates normally bring breaking changes and that is not what I expect in a released distro. One can't know how people are using docker out there. there isn't only atomic/kubernetes out there.

But maybe docker folks are very agile. ;-)

@vinzentm I tend to agree with you the thought was to put it in updates-testing, without ever releasing it so is is easy to get a hold of for those that want it.

@dwalsh reading about updates-testing definition: isn't this thought to test updates which will land in base or updates? Is this also the channel to give preview versions of a next release?

I much like debians backports concept. where selected next release packages are backported to the current release and users can opt-in to use a single package.

I don't believe Fedora has such a capability.

The Fedora approach would be to create a Copr.

Will docker already be at 1.14 by the time f26 ships? I say it's better to test thoroughly in updates-testing and then push to stable when it's ready than flatly ban major docker updates within a Fedora release.

Once the team has consensus on the preferred approach, it would be good to bring it to FESCo to make an official exception to the updates policy. (See https://fedoraproject.org/wiki/Updates_Policy#Exceptions)

Sure, our teams policy is that we don't update docker package until k8s and OpenShift support it. But it is likely that this would change during the 13 months of a Fedora release.

The docker and docker-latest are both at docker 1.12.6, could it be docker at 1.12.6 and docker latest at 1.13 ?

@runcom any chance of making a 1.13 for docker-latest for f25? I think we pretty much decided against going to 1.13 for now.

looks like this probably isn't going to happen and we are almost to f26 so not much reason to waste the effort here. i'm going to close this.