Why was this fork created ?

[afbjorklund]

It doesn't seem to be compatible with docker-machine or the libmachine driver framework ?

[afbjorklund]

@cfergeau

[cfergeau]

It was meant to be used in https://github.com/crc-org/vfkit which is in turn used by a machine-driver internal to crc, but it turns out not to be useful for now, this could be removed if this causes confusion.

[afbjorklund]

Just wondered, the whole machine-drivers organization is something of driftwood...

If you are not going to use it for doing any development, you could archive it perhaps.

[gbraad]

Code-Hex#159 (comment)
@AkihiroSuda Seems you also share the same frustrations...

[afbjorklund]

@gbraad maybe create it ("vz") in the crc-org organization instead, like "vfkit"?

• Use alternative 'upstream' for driver bindings crc-org/vfkit#10 (comment)

Minikube is still using the libmachine framework, and it now has a vfkit driver...

https://github.com/kubernetes/minikube/tree/master/pkg/drivers/vfkit

[gbraad]

we have shared interests among several projects to use

note: this is mostly created for the discussion

[gbraad]

I hope you realize that the driver you referenced relies on the built binary that we maintain. the issue is that the swift bindings we use are poorly maintained; the maintainer refuses or ignores requests. this has been ongoing for quite a while and would be detrimental also for the visit driver of minikube if we can't get patches or features included, and/or worked on by multiple people.

https://github.com/kubernetes/minikube/blob/master/pkg%2Fdrivers%2Fvfkit%2Fvfkit.go#L254

[afbjorklund]

Oh indeed, but as far as I know there are no docker-machine drivers for vz - so the machine-drivers organization is the wrong place for hosting vz. Especially since it is about to be retired? Here was the issue opened for the collaboration:

• vfkit now included in minikube, as replacement for hyperkit crc-org/vfkit#187

And it (vfkit) seems to accept submissions just fine, outside of CRC and Podman Desktop :-)

[afbjorklund]

Also I do think that the original maintainer (of Vz) is looking for funding, in order to start a supporting project for it.

https://github.com/Code-Hex/vz/issues

[afbjorklund]

The last remaining fork might continue into 2025, but still... The docker-machine drivers are running on life support.

https://gitlab.com/gitlab-org/ci-cd/docker-machine/-/commit/626d13ee78c1845ea22fe27756463b0c2776cb37

[gbraad]

vfkit depends on the vz (swift bindings).

[gbraad]

funding

money talks, but does not change attitude. Several people in that repo have raised concerns. We are looking for a reliable way to contribute, with likewise-minded people.

machine-drivers might not even be the right place, but a good place to start the discussion until we find a good home.