-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Docker, from 17.06 to 17.09 #2427
Conversation
17.12.0 seems to fail horribly, will try with 17.09.0 instead
|
Thanks! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund, dlorenc The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
The reason that 17.12.0 didn't work was because DOCKER_RAMDISK stopped working in containerd: It has been fixed in the 18.02 release, so we will be able to upgrade to 18.03.0-ce once it comes out. |
@afbjorklund Maybe for now it makes sense to upgrade to 17.12.1?
|
I just compiled ISO locally - it seems to be working
|
@karser : sure, that would work too... |
@karser : added a PR, we'll see how it goes.. |
18.03.0-ce has been released |
@karser : and yet, only 17.03 is supported: (by https://kubernetes.io/docs/setup/independent/install-kubeadm/#installing-docker
Think we should rest on 17.12, at least for a month or so ? https://docs.docker.com/install/#time-based-release-schedule
Still cleaning up after the 1.12.6 to 1.13.1 rebase on CentOS... |
Ugh, that's an ancient one
For me, it's not like that. 17.12 allows to copy a folder and set the ownership in one step, e.g: |
The 17.12.1-ce release should already be the default: cc965e3 But since there hasn't been a new ISO/distro release, you will need to compile your own buildroot... @r2d4: Maybe it is time to bump the ISO_VERSION to I guess some people use the minikube docker as their main docker, and thus need newer versions. |
No description provided.