From 881b48a3b61bd10f4ade900a4a4dab6c6a0c63f6 Mon Sep 17 00:00:00 2001 From: Justin Chadwell Date: Fri, 8 Jul 2022 15:32:41 +0100 Subject: [PATCH] docs: fixup remote builder typos - Ensure that buildx is always used as a docker subcommand - Correct invalid buildx ls output Signed-off-by: Justin Chadwell --- docs/guides/remote-builder.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/guides/remote-builder.md b/docs/guides/remote-builder.md index 7104d938..837fe21d 100644 --- a/docs/guides/remote-builder.md +++ b/docs/guides/remote-builder.md @@ -45,7 +45,7 @@ srw-rw---- 1 root user 0 May 5 11:04 /home/user/buildkitd.sock You can then connect buildx to it with the remote driver: ```console -$ buildx create \ +$ docker buildx create \ --name remote-unix \ --driver remote \ unix://$HOME/buildkitd.sock @@ -54,10 +54,10 @@ $ buildx create \ If you list available builders, you should then see `remote-unix` among them: ```console -$ buildx ls +$ docker buildx ls NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS -test remote - test0 unix:///home/.../buildkitd.sock running linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386 +remote-unix remote + remote-unix0 unix:///home/.../buildkitd.sock running linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386 default * docker default default running linux/amd64, linux/386 ```