Make running in the background the default

[germag]

We are moving to integrate this tool in podman, so we need to follow the podman command line convention. So, let's make running in the background the default behavior requiring -i/--interactive to spawn an SSH session.

Related #1

[rhatdan]

Podman runs containers in the background using --detach, -d

   --detach, -d
       Detached mode: run the container in the  background  and
       print the new container ID. The default is false.

--interactive is to connect stdin to the application. So if podman bootc allowed users to enter their user name and password when prompted after the OS bootc.

[cgwalters]

Before we make substantial UX changes let's do a tagged release so that we have a stable reference point, and anyone who wants to pin can do so.

[germag]

Podman runs containers in the background using --detach, -d

   --detach, -d
       Detached mode: run the container in the  background  and
       print the new container ID. The default is false.

--interactive is to connect stdin to the application. So if podman bootc allowed users to enter their user name and password when prompted after the OS bootc.

Yes,

I'm not sure if we can map 1:1 podman behavior. We can add --detach, -d as default (plus printing the VM id), but I think we only have two modes, interactive (spawning an ssh session) or background (without spawning an ssh session)

[rhatdan]

SGTM. Bottom line look at how Podman does something and then match the Podman CLI options if possible.