Update README and examples with the new cmd format

Update the README and the examples to reflect the changes in the
handling of command line arguments for the application. In particular,
replace cmdline with cmd in bunnyfile and the cmdline annotation with
CMD in Containerfiles.

Signed-off-by: Charalampos Mainas <cmainas@nubificus.co.uk>

Author: cmainas

README.md

@@ -62,7 +62,7 @@ kernel:                                         # [5] Specify a prebuilt kernel
   from: local                                   # [5a] Specify the source of a prebuilt kernel.
   path: local                                   # [5b] The path where the kernel image resides.
 
-cmdline: hello                                  # [6] The cmdline of the app.
+cmd: ["hello"]                                  # [6] The command line arguments of the app.
 
 ```
 
@@ -178,7 +178,7 @@ kernel:
   from: local
   path: kernel
 
-cmdline: /server
+cmd: ["/server"]
 ```
 
 We can then package everything with the following command:
@@ -193,7 +193,7 @@ The above `bunnyfile` will perform the following steps:
 2. Copy the file `kernel` from the local build context to the OCI image we used
    in the previous step at `/boot/kernel`.
 3. Set up [`urunc`'s annotations](https://urunc.io/image-building/#annotations)
-   using all the information in the file (e.g. framework, version, cmdline,
+   using all the information in the file (e.g. framework, version, cmd,
    binary, initrd).
 4. Produce the final OCI image.
 

examples/CHTTP_Unikraft.md

@@ -1,7 +1,7 @@
 # Creating the initrd and packaging a Unikraft unikernel with `bunny`
 
 For this example, we will use the [C HTTP Web
-Server](https://github.com/unikraft/catalog/tree/main/examples/http-c) example
+Server](https://github.com/unikraft/catalog/tree/main/examples/httpserver-gcc13.2) example
 in Unikraft's catalog. To build the unikernel, we mainly need to:
 1. Build the C HTTP server
 2. Create the initrd for Unikraft
@@ -52,10 +52,14 @@ To package everything together, we can use the following `Containerfile`:
 #syntax=harbor.nbfc.io/nubificus/bunny:latest
 FROM unikraft.org/base:latest
 
+COPY rootfs.cpio /rootfs.cpio
+
 LABEL com.urunc.unikernel.binary="/unikraft/bin/kernel"
-LABEL "com.urunc.unikernel.cmdline"="/chttp"
+LABEL "com.urunc.unikernel.initrd"="/rootfs.cpio"
 LABEL "com.urunc.unikernel.unikernelType"="unikraft"
 LABEL "com.urunc.unikernel.hypervisor"="qemu"
+
+CMD ["/chttp"]
 ```
 
 ## Using a `bunnyfile`
@@ -84,7 +88,7 @@ kernel:
   from: unikraft.org/base:latest
   path: /unikraft/bin/kernel
 
-cmdline: /chttp
+cmd: ["/chttp"]
 ```
 
 With the above bunnyfile`, `bunny` will build the rootfs of Unikraft as a cpio

examples/Nginx_Unikraft.md

@@ -1,6 +1,6 @@
 # Packaging a Unikraft unikernel with `bunny`
 
-For this example, we will use an existing [Unikraft](unikraft.org) Unikernel
+For this example, we will use an existing [Unikraft](https://unikraft.org/) Unikernel
 image from [Unikraft's catalog](https://github.com/unikraft/catalog), we can
 transform it to an image that [urunc](https://github.com/nubificus/urunc) can
 execute with `bunny`. The respective `Containerfile` that we would use with
@@ -11,9 +11,10 @@ execute with `bunny`. The respective `Containerfile` that we would use with
 FROM unikraft.org/nginx:1.15
 
 LABEL com.urunc.unikernel.binary="/unikraft/bin/kernel"
-LABEL "com.urunc.unikernel.cmdline"="nginx -c /nginx/conf/nginx.conf"
 LABEL "com.urunc.unikernel.unikernelType"="unikraft"
 LABEL "com.urunc.unikernel.hypervisor"="qemu"
+
+CMD ["-c", "/nginx/conf/nginx.conf"]
 ```
 
 In order to use `bunny`, instead, we need to specify the
@@ -33,7 +34,7 @@ kernel:
   from: unikraft.org/nginx:1.15
   path: /unikraft/bin/kernel
 
-cmdline: nginx -c /nginx/conf/nginx.conf
+cmd: ["-c", "/nginx/conf/nginx.conf"]
 ```
 
 ## Building the image with bunny as buildkit's frontend

examples/Redis_Rumprun.md

@@ -11,16 +11,18 @@ The respective `Containerfile` that we would use with
 [bima](https://github.com/nubificus/bima) would be:
 
 ```
-#syntax=harbor.nbfc.io/nubificus/pun:latest
+#syntax=harbor.nbfc.io/nubificus/bunny:latest
 FROM scratch
 
 COPY redis.hvt /unikernel/redis.hvt
-COPY redis.conf /conf/redis.conf
+COPY /conf /
 
 LABEL com.urunc.unikernel.binary=/unikernel/redis.hvt
-LABEL "com.urunc.unikernel.cmdline"="redis-server /data/conf/redis.conf"
 LABEL "com.urunc.unikernel.unikernelType"="rumprun"
 LABEL "com.urunc.unikernel.hypervisor"="hvt"
+LABEL "com.urunc.unikernel.mountRootfs"="true"
+
+CMD ["redis-server", "/data/conf/redis.conf"]
 ```
 
 In order to use `bunny`, instead, we need to specify the
@@ -40,13 +42,13 @@ rootfs:
   from: scratch
   type: raw
   include:
-  - redis.conf:/data/conf/redis.conf
+  - conf/:/conf
 
 kernel:
   from: local
   path: redis.hvt
 
-cmdline: "redis-server /data/conf/redis.conf"
+cmd: ["redis-server", "/data/conf/redis.conf"]
 ```
 
 > **NOTE**: Since we use the raw type for rootfs, all the files in the include list