chore (docs): make getting started steps more helpful

Unify the way firecracker binary is made available in a directory
so that it is easier for the users to copy pase the commands with
less modifications.

Signed-off-by: Sudan Landge <[email protected]>

Author: Sudan Landge

docs/getting-started.md

@@ -115,7 +115,7 @@ To instead build firecracker from source, you will need to have `docker` install
 ARCH="$(uname -m)"
 
 # Clone the firecracker repository
-git clone https://github.com/firecracker-microvm/firecracker
+git clone https://github.com/firecracker-microvm/firecracker firecracker_src
 
 # Start docker
 sudo systemctl start docker
@@ -127,10 +127,10 @@ sudo systemctl start docker
 # This will produce the firecracker and jailer binaries under
 # `./firecracker/build/cargo_target/${toolchain}/debug`.
 #
-sudo ./firecracker/tools/devtool build
+sudo ./firecracker_src/tools/devtool build
 
 # Rename the binary to "firecracker"
-mv ./firecracker/build/cargo_target/${ARCH}-unknown-linux-musl/debug/firecracker firecracker
+sudo cp ./firecracker_src/build/cargo_target/${ARCH}-unknown-linux-musl/debug/firecracker firecracker
 ```
 
 ### Starting Firecracker
@@ -143,11 +143,10 @@ process via HTTP requests:
 API_SOCKET="/tmp/firecracker.socket"
 
 # Remove API unix socket
-rm -f $API_SOCKET
+sudo rm -f $API_SOCKET
 
 # Run firecracker
-./firecracker/build/cargo_target/${ARCH}-unknown-linux-musl/debug/firecracker \
-    --api-sock "${API_SOCKET}"
+sudo ./firecracker --api-sock "${API_SOCKET}"
 ```
 
 In a new terminal (do not close the 1st one):