Danm does not work with cri-o (or any container runtime except docker) about danm HOT 7 CLOSED

I can confirm that "ipvlan" networks can be created in pods started with cri-o.

from danm.

Project is only compliant with Docker, but not with other runtimes.

from danm.

Basically it is just a question of using the right Client towards the run-time, but at the moment we only support connecting to a Docker engine, as this is the most popular use-case out there.
Theoretically speaking choosing the right client could be made configurable ofc.

from danm.

I think you can be "container runtime agnostic" as other CNI plugins seem to be. Copy some code from the main cni plugins. I think I can use delegated CNI's just not the built-in's. My CNI plugin for the main k8s network is "bridge" and works fine.

from danm.

Yep, we definitely can be! It is just we are not, at the moment.
Basically we are using "docker inspect" to figure out the netns of the infra Pod from its CID, and this is the only reason we have a docker client in the code.
But the same info can be gathered via direct means too, you are right.

We discussed it internally and @rospring will look into it! Thanks for the find.
Always happy to hear how other people would be / are using the project :)

from danm.

We will correct it soon. netns is coming when cni is invoked.

from danm.

Fixed with #26

from danm.