Replace moby build with linuxkit build throughout

Signed-off-by: Justin Cormack <justin.cormack@docker.com>

docs/platform-aws.md

@@ -22,7 +22,7 @@ export AWS_REGION=eu-west-1
 AWS requires a `RAW` image. To create one:
 
 ```
-$ moby build -format aws examples/aws.yml
+$ linuxkit build -format aws examples/aws.yml
 ```
 
 ## Push image

docs/platform-azure.md

@@ -2,7 +2,7 @@
 
 This is a quick guide to running VMs based on LinuxKit images on Azure. Please note that these images currently do not include the [Azure Linux Agent](https://github.com/Azure/WALinuxAgent). As a result, after creating the VM, the portal will report that the creation failed. If you created the VHD properly, you will still be able to SSH into the machine.
 
-When running `linuxkit run azure`, the image you created using `moby build` will be uploaded to Azure in a resource group, and a VM will be created, along with the necessary resources (virtual network, subnet, storage account, network security group, public IP address).
+When running `linuxkit run azure`, the image you created using `linuxkit build` will be uploaded to Azure in a resource group, and a VM will be created, along with the necessary resources (virtual network, subnet, storage account, network security group, public IP address).
 
 Since Azure does not offer access to the serial output of the VM, you need to have SSH access to the machine in order to attach to it. Please see the example below.
 
@@ -23,7 +23,7 @@ here](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-gro
 
 ## Build an image
 
-Create a new `azure.yml` file [based on the Azure example](../examples/azure.yml), generate a new SSH key and add it in the `yml`, then `moby build -format vhd azure.yml`.
+Create a new `azure.yml` file [based on the Azure example](../examples/azure.yml), generate a new SSH key and add it in the `yml`, then `linuxkit build -format vhd azure.yml`.
 
 
 This will output a `azure.vhd` image.

docs/platform-gcp.md

@@ -50,11 +50,11 @@ Make sure to download the credentials in JSON format and store them somewhere sa
 
 ## Build an image
 
-When using `moby build ...` to build an image, specify `-format gcp` to
+When using `linuxkit build ...` to build an image, specify `-format gcp` to
 build an image in a format that GCP will understand. For example:
 
 ```
-moby build -format gcp myprefix.yml
+linuxkit build -format gcp myprefix.yml
 ```
 
 This will create a local `myprefix.img.tar.gz` compressed image file.

docs/platform-packet.md

@@ -55,7 +55,7 @@ For example, to boot the [example](../examples/packet.net)
 with a local HTTP server:
 
 ```sh
-moby build packet.yml
+linuxkit build packet.yml
 # run the web server
 # run 'ngrok http 8080' in another window
 PACKET_API_KEY=<API key> PACKET_PROJECT_ID=<Project ID> \
@@ -63,7 +63,7 @@ linuxkit run packet -serve :8080 -base-url <ngrok url> packet
 ```
 
 To boot a `arm64` image for Type 2a machine (`-machine
-baremetal_2a`) you currently need build using `moby build packet.yml packet.arm64.yml` and then un-compress both the kernel and
+baremetal_2a`) you currently need build using `linuxkit build packet.yml packet.arm64.yml` and then un-compress both the kernel and
 the initrd before booting, e.g:
 
 ```sh

docs/platform-rpi3.md

@@ -22,7 +22,7 @@ build. See the [`kernel`](./kernels.md) documentation for details.
 
 We use the mainline Linux kernels for the Raspberry Pi and it is
 booted via [`uboot`](https://www.denx.de/wiki/U-Boot). The `moby`
-tool, via `moby build -format rpi3 <YAML>`, currently produces a `tar`
+tool, via `linuxkit build -format rpi3 <YAML>`, currently produces a `tar`
 archive which can be extracted onto a FAT32 formatted SD card to boot
 your Raspberry Pi.
 

docs/platform-vmware.md

@@ -21,7 +21,7 @@ Supported (Tested) versions:
 ## Run
 ### VMware Workstation/Fusion
 The backend `vmware` currently supports the booting of a `.vmdk` file that is
-created through the `moby build -format vmdk` command and is typically called with
+created through the `linuxkit build -format vmdk` command and is typically called with
 `linuxkit run vmware <args> ./path`.
 
 The WS/Fusion backend will construct a config version 8 (Hardware version 12)
@@ -30,7 +30,7 @@ use the `vmrun` utility to start the virtual machine.
 
 ### VMware vSphere/vCenter
 The backend `vsphere` currently supports booting through an `iso` file that is
-created through the `moby build -o iso-bios` and is started with `linuxkit run
+created through the `linuxkit build -o iso-bios` and is started with `linuxkit run
 vcenter <args> ./path`.
 
 The vSphere/vCenter backend requires a user to have `pushed` a linuxkit `iso` to