Add support for stdin-once

[lefinal]

Feature request description

This feature request comes from working with the Docker Go SDK that allows setting StdinOnce when creating a container. This closes stdin for the container after the first attached client (to stdin) disconnects.
Podman currently does not support this, so applications that read from an input stream (in this case stdin) will hang until stopped manually.

Suggest potential solution

Add an stdin-once flag for container creation. If set, stdin to the container is closed after the first attached client (to stdin) disconnects.

Have you considered any alternatives?

No response

Additional context

The struct in Docker Go SDK:
https://pkg.go.dev/github.com/docker/[email protected]+incompatible/api/types/container#Config

Already existing annotation for container inspect details in Podman Go bindings:

podman/libpod/define/container_inspect.go

Line 35 in 46ca057

StdinOnce bool `json:"StdinOnce"`

[rhatdan]

Interested in opening a PR?

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

@Luap99 PTAL

[lefinal]

Sorry for the late reply. I tried to look into it but I am having a hard time understanding the codebase. From what I got, it seems like conmon does not have support for this. I already opened a discussion at containers/conmon#459 but got no response, yet.

[Luap99]

A command like podman-remote run --rm -i alpine cat - <<<"test" works so this should technically already work without such parameter. cat - wouldn't exit if the stdin is not closed.

[Luap99]

This was the fix for it it: fbce758
So as long a your client closes the writing side of the socket it should behave correctly.

That of course does not need to mean that we shouldn't support this API parameter.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.