The status of the issue: `moving to docker 1.13 in Fedora 25` of project:
`atomic-wg` has been updated to: Closed as Wontfix by dustymabe.
https://pagure.io/atomic-wg/issue/196
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe
dustymabe added a new comment to an issue you are following:
``
@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.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
strigazi added a new comment to an issue you are following:
``
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 ?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
dwalsh added a new comment to an issue you are following:
``
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.
``
To reply, visit the link below or just reply to
jasonbrooks added a new comment to an issue you are following:
``
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.
``
To reply,
mattdm added a new comment to an issue you are following:
``
The Fedora approach would be to create a
[Copr](https://copr.fedorainfracloud.org/).
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
___
dwalsh added a new comment to an issue you are following:
``
I don't believe Fedora has such a capability.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
___
cloud mailing list --
vinzentm added a new comment to an issue you are following:
``
@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.
dwalsh added a new comment to an issue you are following:
``
@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.
``
To reply, visit the link below or just reply to this email
dustymabe added a new comment to an issue you are following:
``
-1 on docker 1.13 for now: https://twitter.com/jbeda/status/826969113801093121
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
___
cloud
dwalsh added a new comment to an issue you are following:
``
None have been created yet. I will attempt to get one built as soon as we have
docker-1.13 in updates-testing.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
strigazi added a new comment to an issue you are following:
``
> 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
On Jan 18, 2017 22:46, "Dusty Mabe" wrote:
dustymabe added a new comment to an issue you are following:
``
> I think we should get docker-1.13 into Rawhide right away.
Yup, I'm going to build it there ASAP.
agree on this point. The discussion was meant to target f25.
``
dustymabe added a new comment to an issue you are following:
``
> I think we should get docker-1.13 into Rawhide right away.
agree on this point. The discussion was meant to target f25.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
dwalsh added a new comment to an issue you are following:
``
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
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
In the meeting today @runcom brought up the topic of:
- removing docker-latest in Fedora (mail thread on that
16 matches
Mail list logo