README: move Running to the top

While users install once, they likely need to look up usage instructions
more often.  So move these to the top of the README.

Signed-off-by: Valentin Rothberg <[email protected]>

Author: vrothberg

README.md

@@ -9,6 +9,50 @@ in alignment with the <https://github.com/containers/bootc> project.
 - Be a backend for <https://github.com/containers/podman-desktop-extension-bootc>
 - Work on both MacOS and Linux
 
+## Running
+
+The core command right now is:
+
+```shell
+podman-bootc run <imagename>
+```
+
+This command creates a new virtual machine, backed by a persistent disk
+image from a "self install" of the container image, and makes a SSH
+connection to it.
+
+This requires SSH to be enabled by default in your base image; by
+default an automatically generated SSH key is injected via a systemd
+credential attached to qemu.
+
+Even after you close the SSH connection, the machine continues to run.
+
+### Other commands:
+
+- `podman-bootc list`: List running VMs
+- `podman-bootc ssh`: Connect to a VM
+- `podman-bootc rm`: Remove a VM
+
+### Architecture
+
+At the current time the `run` command uses a
+[bootc install](https://containers.github.io/bootc/bootc-install.html)
+flow - where the container installs itself executed in a privileged
+mode inside the podman-machine VM.
+
+The installation target is a raw disk image is created on the host, but loopback
+mounted over virtiofs/9p from the podman-machine VM.
+
+(The need for a real-root privileged container to write Linux filesystems is part of the
+ rationale for requiring podman-machine even on Linux is that
+ it keeps the architecture aligned with MacOS (where it's always required))
+
+In the future, support for installing via [Anaconda](https://github.com/rhinstaller/anaconda/)
+and [bootc-image-builder](https://github.com/osbuild/bootc-image-builder)
+will be added.
+
+## Installation
+
 ### MacOS
 
 First be sure you have the Podman Desktop [bootc extension requirements](https://github.com/containers/podman-desktop-extension-bootc?tab=readme-ov-file#requirements).
@@ -67,46 +111,3 @@ To compile it, just run in the project directory:
 ```shell
 make
 ```
-
-
-## Running
-
-The core command right now is:
-
-```shell
-podman-bootc run <imagename>
-```
-
-This command creates a new virtual machine, backed by a persistent disk
-image from a "self install" of the container image, and makes a SSH
-connection to it.
-
-This requires SSH to be enabled by default in your base image; by
-default an automatically generated SSH key is injected via a systemd
-credential attached to qemu.
-
-Even after you close the SSH connection, the machine continues to run.
-
-### Other commands:
-
-- `podman-bootc list`: List running VMs
-- `podman-bootc ssh`: Connect to a VM
-- `podman-bootc rm`: Remove a VM
-
-### Architecture
-
-At the current time the `run` command uses a
-[bootc install](https://containers.github.io/bootc/bootc-install.html)
-flow - where the container installs itself executed in a privileged
-mode inside the podman-machine VM.
-
-The installation target is a raw disk image is created on the host, but loopback
-mounted over virtiofs/9p from the podman-machine VM.
-
-(The need for a real-root privileged container to write Linux filesystems is part of the
- rationale for requiring podman-machine even on Linux is that
- it keeps the architecture aligned with MacOS (where it's always required))
-
-In the future, support for installing via [Anaconda](https://github.com/rhinstaller/anaconda/)
-and [bootc-image-builder](https://github.com/osbuild/bootc-image-builder)
-will be added.