witty-honey-18052
07/25/2022, 3:15 PMInvalid Plugins:
buildx failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-buildx: no such file or directory
scan failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-scan: no such file or directory
:~/.docker/cli-plugins$ ls
docker-compose
From tracking through the github issues, this looks like it should be downloaded and installed automatically. On the two machines I checked with 1.4.1, it isn't. Should it be?C:\code [main ≡ +0 ~2 -0 !]> docker buildx version
<http://github.com/docker/buildx|github.com/docker/buildx> v0.7.1 05846896d149da05f3d6fd1e7770da187b52a247
C:\code [main ≡ +0 ~2 -0 !]> docker-buildx version
<http://github.com/docker/buildx|github.com/docker/buildx> v0.8.2 6224def4dd2c3d347eee19db595348c50d7cb491
Is it a bug/issue how the hyphenated command has a different version?jolly-forest-99711
07/25/2022, 11:25 PMdocker-buildx
in WSL distros. We should definitely have this!
Regarding the differing versions of docker buildx
and docker-buildx
, I see the same thing on my Windows install. I had thought that the only place the docker CLI would pick plugins up from was ~/.docker/cli-plugins
, but I'm clearly wrong because I don't see anything in this directory, and yet I can call docker buildx
witty-honey-18052
07/25/2022, 11:25 PMjolly-forest-99711
07/25/2022, 11:26 PMwitty-honey-18052
07/25/2022, 11:26 PMjolly-forest-99711
07/25/2022, 11:28 PMPATH
that takes precedencewitty-honey-18052
07/25/2022, 11:28 PMjolly-forest-99711
07/26/2022, 3:47 PMdocker-buildx
. We should probably make it generic, since I believe there are plans to integrate more docker CLI plugins