Upgrade cri-dockerd version to fix a bug that can not download large images

[tenzen-y]

Signed-off-by: tenzen-y yuki.iwai.tz@gmail.com

The cri-dockerd v0.2.0 has a critical bug that can not download large container images. And it was resolved in v0.2.6.

ref:

• Can't pull modestly sized image from Quay.io kubernetes/minikube#14789
• Use context.WithCancel for potentially long operations Mirantis/cri-dockerd#108
• Mirantis/cri-dockerd@460da8e

[manusa]

Nice!
The asset filtering needs to be tuned since now the Linux artifact no longer contains linux in its name. I'll change this if I can later today (feel free to do so yourself if I haven't responded in a few hours).

[tenzen-y]

Nice!
The asset filtering needs to be tuned since now the Linux artifact no longer contains linux in its name.

Thanks for the review!

I'll change this if I can later today (feel free to do so yourself if I haven't responded in a few hours).

Thanks for your effort!

[manusa]

LGTM, thx!

[tenzen-y]

@manusa Thanks for improving a mechanism to install cri-dockerd!

[manusa]

@manusa Thanks for improving a mechanism to install cri-dockerd!

still WIP ;)

[tenzen-y]

@manusa Thanks for improving a mechanism to install cri-dockerd!

still WIP ;)

:_(

[manusa]

Unfortunately Minikube's support for cri-dockerd v0.2.6 is not there yet (kubernetes/minikube#14724).

I'm trying to figure out a proper way to setup cri-dockerd with a cni plugin, but still no luck.

I'm also not sure if the problems with the ingress and registry extensions are related to this, or to something else.

[tenzen-y]

Unfortunately Minikube's support for cri-dockerd v0.2.6 is not there yet (kubernetes/minikube#14724).

I'm trying to figure out a proper way to setup cri-dockerd with a cni plugin, but still no luck.

I'm laso not sure if the problems with the ingress and registry extensions are related to this, or to something else.

@manusa Thanks for clarifying.
Maybe, we need to wait for releasing version included kubernetes/minikube#14827.

[manusa]

Upgrading cri-docker required the update of the complete ecosystem.

After waiting multiple months for everything to work, it seems that the dependency combination provided in #95 does the trick.

Your commit was cherry-picked into that PR, will merge that one while closing this one.

Thx for your contribution.

[tenzen-y]

Upgrading cri-docker required the update of the complete ecosystem.

After waiting multiple months for everything to work, it seems that the dependency combination provided in #95 does the trick.

Your commit was cherry-picked into that PR, will merge that one while closing this one.

Thx for your contribution.

Thank you for your hard work!