[CI:DOCS] generate systemd: clarify limitations of --new

[vrothberg]

generate systemd --new is looking at the "create command" of the
container/pod which is simply the os.Args at creation time.

It does not work on containers or pods created via the REST API since
the create command is not set. --new does work on such containers and
pods since there is no reliable way to reverse-map their configs to
command-line arguments of podman.

Fixes: #11370
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]

@containers/podman-maintainers PTAL

[vrothberg]

@Luap99 PTAL

[Luap99]

LGTM

[Luap99]

I just want to point out that this is also a potential problem for podman clone and podman rename. The create command will no longer contain the correct command when settings are changed, e.g. the name.

[vrothberg]

I just want to point out that this is also a potential problem for podman clone and podman rename. The create command will no longer contain the correct command when settings are changed, e.g. the name.

Fair point. The text explicitly states that only create/run is supported. Everything else is excluded.

[vrothberg]

Merge me?

[rhatdan]

/lgtm