docker/buildx
1
0
Fork 0
mirror of https://gitea.com/Lydanne/buildx.git synced 2025-05-29 08:57:44 +08:00
Code Issues Packages Projects Releases 1 Wiki Activity

docs: fixup remote builder typos

Browse Source 
- Ensure that buildx is always used as a docker subcommand
- Correct invalid buildx ls output

Signed-off-by: Justin Chadwell <me@jedevc.com>
This commit is contained in:
Justin Chadwell 2022-07-08 15:32:41 +01:00
parent 5b452b72a2
commit 881b48a3b6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/guides/remote-builder.md
View File

@ -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: You can then connect buildx to it with the remote driver:
```console ```console
$ buildx create \ $ docker buildx create \
--name remote-unix \ --name remote-unix \
--driver remote \ --driver remote \
unix://$HOME/buildkitd.sock unix://$HOME/buildkitd.sock
@ -54,10 +54,10 @@ $ buildx create \
If you list available builders, you should then see `remote-unix` among them: If you list available builders, you should then see `remote-unix` among them:
```console ```console
$ buildx ls $ docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS
test remote remote-unix remote
test0 unix:///home/.../buildkitd.sock running linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386 remote-unix0 unix:///home/.../buildkitd.sock running linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386
default * docker default * docker
default default running linux/amd64, linux/386 default default running linux/amd64, linux/386
``` ```