-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ls: display buildkit version of the nodes #998
Conversation
30723ec
to
81eac7b
Compare
commands/util.go
Outdated
inf, err := c.Info(ctx) | ||
if err != nil { | ||
if st, ok := grpcerrors.AsGRPCStatus(err); ok && st.Code() == codes.Unimplemented { | ||
d.version = "N/A" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should have a fallback for it. Version can be queried by running --version
on buildkitd
or from docker version
for docker driver. We could add this in the driver interface and let it decide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added fallback for docker-container
and docker
driver. Left unimplemented for kubernetes
and remote
drivers for now (cc @jedevc @AkihiroSuda):
$ docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
builder2 docker-container
builder20 unix:///var/run/docker.sock running v0.10.3 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
builder3 docker-container
builder30 unix:///var/run/docker.sock running v0.10.3 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
builder4 * docker-container
builder40 unix:///var/run/docker.sock running v0.10.0-91-g86c33b66 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
xenodochial_davinci docker-container
xenodochial_davinci0 unix:///var/run/docker.sock running v0.9.3 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
desktop-linux protocol not available
default docker
default default running 20.10.14 linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - I don't think there's a good way to work out what version the remote
driver is running if the gRPC call fails
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
81eac7b
to
57156ee
Compare
Yeah, still wondering a bit what information is most relevant in the overview. The "staggered" / alternating lines, together with the long list of (possible) architectures supported make the list hard to "grasp" in a quick look. I'm also trying to find what order is used to print these (doesn't appear to be ordered by A more "toned-down" representation with one item per line could look like; docker buildx ls
NAME NODE DRIVER STATUS BUILDKIT PLATFORMS
builder2 builder20 docker-container running N/A linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
builder3 builder30 docker-container running 86c33b6 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
builder4 * builder40 docker-container running v0.10.0-91-g86c33b66 linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
default default docker running N/A linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
desktop-linux default docker running N/A linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
xenodochial_davinci xenodochial_davinci0 docker-container running N/A linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6 Or even (omitting the docker buildx ls
NAME NODE DRIVER STATUS BUILDKIT
builder2 builder20 docker-container running N/A
builder3 builder30 docker-container running 86c33b6
builder4 * builder40 docker-container running v0.10.0-91-g86c33b66
default default docker running N/A
desktop-linux default docker running N/A
xenodochial_davinci xenodochial_davinci0 docker-container running N/A The |
@thaJeztah I will continue working on #830 based on your comment here and this one #830 (comment) |
needs moby/buildkit#2725vendor buildkit to bring moby/buildkit#2725: moby/buildkit@3e38a2d...86c33b6
Maybe we could display this info with a
--no-trunc
flag and not by default. cc @thaJeztahSigned-off-by: CrazyMax crazy-max@users.noreply.github.com