generate kube: Do not print spec.containers.command, if it is the default entrypoint of the image

[dilyanpalauzov]

At #11672 I asked to alter podman generate kube not to print variables, which were not part of the container and not to print spec.containers.command. podman 3.4.0 still prints on podman generate kube the command, even if it is the default commant/entrypoint contained in the image.

As test case I use the instructions from https://mail.aegee.org/cgit/aegee-ldap/tree/readme.md#n13.

[umohnani8]

@dilyanpalauzov to verify, you are saying if the default command/entrypoint defined in the image is used when running the container, it should not show up in the generated kube yaml? Only the command that the user passes in via the command line when doing a podman run should show up in the kube yaml?

So if my image has the command sleep 1000 and I do podman run myimage ls then ls should show up in the kube yaml, but if I just do podman run myimage then nothing should show up under command in the kube yaml?

[dilyanpalauzov]

Exactly.

[Luap99]

This was already fixed in #11704

[dilyanpalauzov]

As mentioned at #11672 (comment) , I tried it, and it does not work for me.

[Luap99]

I see it only works for command but not the entrypoint.