Closed praveenkumar closed 7 years ago
will this update to a new boot2docker with a more recent kernel version? because the current version has a possible issue with Ryzen CPUs: https://github.com/minishift/minishift/issues/1022
@praveenkumar @budhrg I think this relates to issues #26
I am also wondering why we not should update to the latest available version issue #28. Obviously there are cases to be made for either. This pull requests aligns Docker versions between our ISOs. Upgrading to the latest gives user some more features.
I am also wondering why we not should update to the latest available version issue #28.
Right, I think this will resolve #28 also but as I mentioned on the issue, we should have consistent docker version across all our ISO and right now it's 1.12.6
I mentioned on the issue, we should have consistent docker version across all our ISO and right now it's 1.12.6
That's means why not go for 1.13.1 which is the last version before they moved to community edition (CE) kind of version (See here). Let sync this version is CentOS ISO too.
@praveenkumar can we not upgrade the CentOS ISO version as well? Or is there nothing later?
Let sync this version is centos ISO too.
@budhrg , @hferentschik No, docker version which part of centos is comes from offical repo and we don't have ownership there and we should not use unofficial repo for CentOS just for docker version upgrade because same version what stick to our RHEL ISO also.
@praveenkumar Please update commit message with docker version for easy track.
@gbraad let CI run for this and then we can merge this PR.
@praveenkumar CI is fine. Now, it can be merged.
@praveenkumar as per docker
1.12.6
commit, path has now changed from/make_iso.sh
to/tmp/make_iso.sh
. See here https://github.com/boot2docker/boot2docker/commit/f3e4485ff8fb2f5aa81d1f7834a82fa5ec33aeaf.