Machine start from script

[poldolot]

I want to start podman machine from script and when script exits with error I want that machine to stay, but now it gets stopped.

How to reproduce:

1. create script:

#!/bin/bash
podman machine start
echo "sleeping"
sleep 100

2. press ctrl+c after "sleeping" is displayed
3. machine is stopped

When there is no interruption and script exits without error then machine stays running.
I'm working on macOS but the same is under Linux.
I've already tried nohup and trap.

[Honny1]

The terminal will pass the Ctrl-c-triggered SIGINT on to the script's process group. The podman machine will then receive SIGINT and exit. I don't think this is a bug.

WDYT? @baude @jakecorrenti

[jakecorrenti]

We recently added signal handling on podman machine start. If the process receives SIGINT before the VM successfully starts, then it will exit and ensure the state is correct. This is working as expected.

[poldolot]

But machine is successfully started and even after 2 minutes of sleep after podman machine start, when I'll press ctrl+c the machine stops. I'm using version 5.5.0.

[baude]

In the case of Linux, the signint is being passed to the subsequent processes that Podman spawned like qemu, gvproxy, and virtiofsd. Podman exits as soon as the machine is booted.

On a Mac, the same basic thing is presumably happening except that instead of qemu, it would be vfkit or libkrun.