Kubernetes is removing docker shim support

Yorick

Wizard
Joined
Nov 4, 2018
Messages
1,912

That's for 1.24 in April 2022, and 1.23 will remain supported for another year. Still, for the next version of SCALE after this one, migrating to containerd or CRI-O sounds like an excellent move. This could also enable the asked-for docker-compose support, in the form of Podman, as that won't interfere with k3s. And no actual docker daemon will need to run anywhere.
 
Last edited:

nicat23

Cadet
Joined
Jan 14, 2022
Messages
1
I can say that I have worked with a kubernetes cluster that ran on CRI-O and it worked marvelously, 5 node cluster
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
This could also enable the asked-for docker-compose support, in the form of Podman, as that won't interfere with k3s. And no actual docker daemon will need to run anywhere.

Is there any reason why podman would not run now on SCALE 22.02? Has anyone tried it?
 

truecharts

Guru
Joined
Aug 19, 2021
Messages
788

That's for 1.24 in April 2022, and 1.23 will remain supported for another year. Still, for the next version of SCALE after this one, migrating to containerd or CRI-O sounds like an excellent move. This could also enable the asked-for docker-compose support, in the form of Podman, as that won't interfere with k3s. And no actual docker daemon will need to run anywhere.

This has been known for about 2 years by now, the announcement has been made in 2020.
It's not an issue at all and never has been and also already discussed with the iX developers around early 2021 as well.

The correct blog post should've been:
"Kubernetes is halting the INCLUSION of dockershim with it's product"

Which sounds a lot less impressive.

Also:
Kubernetes support is not the driving factor for TrueNAS, it's K3S support.
For all we care, k3s is going to include it anyway.

Even so: A move to containerd instead of dockershim would also be possible, which is a lot less intrusive than CRIO-O

TLDR:
It is not really an issue at this point and relatively trivial to fix in the future.
 
Last edited:
Top