| Message ID | 20180301072012.25884-1-christian@paral.in |
|---|---|
| Headers | show |
| Series | upgrade docker-engine and associated components | expand |
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes: > Hi all, > This series upgrades Docker and associated components: > - runc to 9f9c96235cc97674e935002fc3d78361b696a69e > - docker-containerd to v1.0.2 > - docker-engine to v2018.03.0-ce-rc1 I am far from a docker expert, but isn't this an 'edge' release? Given the Buildroot release schedule, wouldn't it make more sense to use the 'stable' releases with a similar quarterly support/release schedule?
Hi Peter, Peter Korsgaard <peter@korsgaard.com> writes: > > - runc to 9f9c96235cc97674e935002fc3d78361b696a69e > > - docker-containerd to v1.0.2 > > - docker-engine to v2018.03.0-ce-rc1 > > I am far from a docker expert, but isn't this an 'edge' release? Given > the Buildroot release schedule, wouldn't it make more sense to use the > 'stable' releases with a similar quarterly support/release schedule? Yes, it's intended to be merged into "next" for release not in Buildroot 2018.02 but later. I thought I had mentioned that in the cover letter, but I guess that was in another revision, lost somewhere months ago. The reason is because from our testing on various devices with varying container workloads, the only two stable versions (with no critical bugs) of Docker that we have been able to find were early 2017 or 2018.03-rc1. 2018.03-rc1 will be released as a full release soon as 2018.02 was completely unusable due to a "container already exists" error when trying to start a container. If you would like me to make another series based around 17.12.1-ce that was just released, I would be happy to do so. Best, Christian Stewart
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes: > Hi Peter, > Peter Korsgaard <peter@korsgaard.com> writes: >> > - runc to 9f9c96235cc97674e935002fc3d78361b696a69e >> > - docker-containerd to v1.0.2 >> > - docker-engine to v2018.03.0-ce-rc1 >> >> I am far from a docker expert, but isn't this an 'edge' release? Given >> the Buildroot release schedule, wouldn't it make more sense to use the >> 'stable' releases with a similar quarterly support/release schedule? > Yes, it's intended to be merged into "next" for release not in Buildroot > 2018.02 but later. I thought I had mentioned that in the cover letter, > but I guess that was in another revision, lost somewhere months ago. > The reason is because from our testing on various devices with varying > container workloads, the only two stable versions (with no critical > bugs) of Docker that we have been able to find were early 2017 or 2018.03-rc1. That sounds pretty horrible :/ > 2018.03-rc1 will be released as a full release soon as 2018.02 was > completely unusable due to a "container already exists" error when > trying to start a container. > If you would like me to make another series based around 17.12.1-ce that > was just released, I would be happy to do so. Well, only if it actually works. But if you think there will be a new (working) stable release before our next release (E.G. by April) then I'm also fine with going with this 2018.03 version.
Hi Peter, Peter Korsgaard <peter@korsgaard.com> writes: >>>>>> "Christian" == Christian Stewart <christian@paral.in> writes: > > 2018.03-rc1 will be released as a full release soon as 2018.02 was > > completely unusable due to a "container already exists" error when > > trying to start a container. > > > If you would like me to make another series based around 17.12.1-ce that > > was just released, I would be happy to do so. > > Well, only if it actually works. But if you think there will be a new > (working) stable release before our next release (E.G. by April) then > I'm also fine with going with this 2018.03 version. It's probably best to merge this to next for now (or wait until 2018.03 is released) and plan for the next stable release (2018.03) to include in the next Buildroot stable. I'll test the stability of the other release this weekend as well. Best, Christian