-
Notifications
You must be signed in to change notification settings - Fork 2k
Docker Machine v0.5.1 breaks compatibility with v0.5.0 drivers #2325
Comments
Ah, of course, the linting changes. Thanks for the report @janeczku. I'm pretty upset about this (and I really am profusely sorry) as it wasn't intended to break compatibility but I think the linting changes are over (new PRs are being run through |
Yes, that's bad. We had to do it. We should have done it before 0.5.0 and didn't have time. |
That's really sad that backward & forward incompatible stuff was done in the scope of patch level release. May be, it is reasonable to bump a minor version at least? (0.6.0) |
You can still fix this AND keep the linting change. There is no reason to tie the API service and method names to Go types. Please consider reopening, making the change, and restoring the API. Should I send a PR? |
@allingeek Interesting, I had not considered that as an alternative. Would love to see such a PR. |
Addresses docker#2325 Signed-off-by: Jeff Nickoloff <[email protected]> modified: libmachine/drivers/plugin/register_driver.go modified: libmachine/drivers/rpc/client_driver.go
I've verified that a docker-machine binary with this patch will work with both plugin generations. |
@allingeek you rock! 👏 📣 |
Added compatibility for both 5.0 and 5.1 RPC plugins. Addresses docker#2325 Signed-off-by: Jeff Nickoloff <[email protected]> modified: libmachine/drivers/plugin/register_driver.go modified: libmachine/drivers/rpc/client_driver.go
Can this be closed after the patch? |
Yes I think so! |
This particularly affects use of drivers not distributed with the machine binary.
For simplicity this is demonstrated with the
virtualbox
driver.Steps to reproduce
$ git clone https://github.com/docker/machine.git
$ cd machine && git checkout v0.5.0
$ go build -a -o /usr/local/bin/docker-machine-driver-virtualbox cmd/machine-driver-virtualbox.go
$ git checkout v0.5.1
$ go build -a -o /usr/local/bin/docker-machine cmd/machine.go
$ docker-machine create -d virtualbox
Expected result
Machine continuous to work
Actual result
Error occurs and Machine exits
This is probably caused by commit 89d9854 which changed the RPC API interface breaking compatibility with all drivers compiled against v0.5.0 or earlier.
Reference PR #2321
/cc @nathanleclaire @dmp42
The text was updated successfully, but these errors were encountered: