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 [here](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-Janu...)) - moving to docker 1.13 (just released) in Fedora 25
There are some concerns over moving to docker 1.13 but we believe that if we are able to qualify it enough it would be beneficial to go to the latest version so that @runcom doesn't have to manage so many versions of docker. The current proposal is:
- first, wait 4 weeks - let some bugs from initial release work itself out - many of us are traveling over the next few weeks anyway so this won't hurt - 2nd, put out update to updates-testing and wait some time for thorough tests to be conducted on the testing ostree. - If there are big issues with 1.13 that don't have a ready fix (performance issues, complicated issues that don't have fixes) then we can unpush 1.13 from updates-testing and put out security fixes etc for 1.12. We'd like to not have to unpush if possible though.
Another thing that might be useful is a condensed list of changes from 1.12 to 1.13. @runcom, could you provide us with that information?
``
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 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. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/196
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
On Jan 18, 2017 22:46, "Dusty Mabe" pagure@pagure.io 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. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/196 _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org
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 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? ``
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: `` 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
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
dwalsh added a new comment to an issue you are following: `` Awesome. ``
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: `` @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 https://pagure.io/atomic-wg/issue/196
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. where selected next release packages are backported to the current release and users can opt-in to use a single package. ``
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
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
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, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/196
mattdm added a new comment to an issue you are following: `` 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) ``
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 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
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
dustymabe added a new comment to an issue you are following: `` 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. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/196
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.
-
Antonio Murdaca -
Daniel J Walsh -
Dusty Mabe
-
Jason Brooks
-
Matthew Miller
-
Pagure
-
Spyros Trigazis
-
Thomas Mueller