You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 26, 2021. It is now read-only.
If I use Docker Machine v0.5.5 (official build) and docker-machine-driver-parallels built with libmachine ref 204af9f (parent commit of #2636), then I get the following error:
$ MACHINE_DEBUG=1 docker-machine ls... <cut>(b2d-prl) DBG | executing: prlctl list -i b2d-prl(b2d-prl) Calling .GetState(b2d-prl) Calling .DriverNameError attempting call to get driver name: connection is shut downNAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORSb2d-prl - Error Unknown unexpected EOFb2d-vbox - virtualbox Stopped UnknownMaking call to close driver server(b2d-prl) Calling .CloseError closing a plugin driver: connection is shut downMaking call to close driver server(b2d-vbox) Calling .CloseSuccessfully made call to close driver serverMaking call to close connection to plugin binary(b2d-vbox) DBG | Closing plugin on server side
If I rebuild docker-machine-driver-parallels with linking to ref 3b84a94 (or any other, later than #2636), then everything works fine:
(b2d-prl) DBG | Found lease: 10.211.55.197 for MAC: 001C42292CAB, expiring at 1451331030, leased for 1800 s.(b2d-prl) DBG |(b2d-prl) DBG | Found IP lease: 10.211.55.197 for MAC address 001C42292CAB(b2d-prl) DBG |Reading CA certificate from /Users/legal/.docker/machine/certs/ca.pemReading server certificate from /Users/legal/.docker/machine/machines/b2d-prl/server.pemReading server key from /Users/legal/.docker/machine/machines/b2d-prl/server-key.pem(b2d-prl) Calling .DriverNameNAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORSb2d-prl - parallels Running tcp://10.211.55.197:2376 v1.9.1b2d-vbox - virtualbox Stopped UnknownMaking call to close driver server(b2d-prl) Calling .CloseSuccessfully made call to close driver serverMaking call to close connection to plugin binaryMaking call to close driver server(b2d-vbox) Calling .CloseSuccessfully made call to close driver serverMaking call to close connection to plugin binary(b2d-vbox) DBG | Closing plugin on server side
It means that all 3rd-party plugins built with libmachine before #2636 (< 0.5.5) is incompatible with Docker Machine v0.5.5+
Fortunately, the "forward" compatibility is not broken and the plugin built with the latest libmachine could be used with previous versions of Docker Machine. So, you can close this issue due to there is nothing to fix already.
P.s. Folks, please, test the compatibility with 3rd party plugins before publishing the release 🙏. I'd be glad to help you in this - just ping me via e-mail, twitter or GitHub
The text was updated successfully, but these errors were encountered:
We'll keep you more closely in the loop in the future @legal90. Thanks for filing the issue. We still have #2498 open as a work item in the pipe to help with this and we'd like your opinion on the best way to implement it.
Seems like this PR #2636 breaks the backward compatibility with 3rd-party plugins: Parallels/docker-machine-parallels#32
If I use Docker Machine v0.5.5 (official build) and
docker-machine-driver-parallels
built with libmachine ref 204af9f (parent commit of #2636), then I get the following error:If I rebuild
docker-machine-driver-parallels
with linking to ref 3b84a94 (or any other, later than #2636), then everything works fine:It means that all 3rd-party plugins built with libmachine before #2636 (< 0.5.5) is incompatible with Docker Machine v0.5.5+
Fortunately, the "forward" compatibility is not broken and the plugin built with the latest libmachine could be used with previous versions of Docker Machine. So, you can close this issue due to there is nothing to fix already.
P.s. Folks, please, test the compatibility with 3rd party plugins before publishing the release 🙏. I'd be glad to help you in this - just ping me via e-mail, twitter or GitHub
The text was updated successfully, but these errors were encountered: