fix remote run/start flake

[vrothberg]

Fix the flake reported in #9597 with a workaround to at least stop
wasting energy until the root cause has been found and fixed.

It seems that a remote run returns before the container has transitioned
into the exited state which ultimately breaks a subsequent remote
start with attach.

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrothberg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vrothberg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vrothberg]

@edsantiago PTAL

I don't want to close issue #9597 with this PR since the underlying root cause remains unclear. The good news is that the issue is easy to reproduce on my workstation with:

./bin/podman-remote run --replace --name test alpine sh -c 'start=0; if test -s log; then start=tail -n 1 log; fi; seq expr $start + 1 expr $start + 10 | tee -a log'; ./bin/podman-remote start -a test

[vrothberg]

@containers/podman-maintainers PTAL

[umohnani8]

LGTM

[edsantiago]

Tests are green (flake was the usual search one)

[vrothberg]

merge me

[edsantiago]

/lgtm