podman play kube does not not pass CMD (from image) to ENTRYPOINT

[kiancross]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Starting a pod using podman kube play does not pass the CMD option from the image config to ENTRYPOINT.

Conversely, starting the same image using podman run does pass the CMD option from the image (as expected).

This issue did not occur on the previous version of Podman I used: 2.0.5.

Steps to reproduce the issue:

1. Create kube.yml.

#
# kube.yml
#

apiVersion: v1
kind: Pod 

metadata:
  name: test
  creationTimestamp: "2020-10-17T17:49:13Z"

spec:
  containers:
    - name: mongo
      image: docker.io/library/mongo:4

2. Start: podman play kube kube.yml.

3. Run podman run -d docker.io/library/mongo:4.

Describe the results you received:

I would expect the COMMAND (displayed using podman ps --all --no-trunc) to be the same for both containers.

Describe the results you expected:

Output of podman ps --all --no-trunc:

CONTAINER ID                                                      IMAGE                      COMMAND               CREATED        STATUS                     PORTS   NAMES
307f09e350c5dccc7e825e0b30ec53c34b62c892b89d4fac7db6ba6cd72421be  docker.io/library/mongo:4  mongod                4 minutes ago  Up 4 minutes ago                   exciting_meninsky
2eda4ff3dc2fe02ddb4e8c1a8b2d18c2a59f17e05ef20e495d82db7c152e3c2a  docker.io/library/mongo:4  docker-entrypoint.sh  5 minutes ago  Up Less than a second ago          test-mongo
fad48dfa409ace7e38eed99fe0e6cad3ad0380dfc8194826019907fa9c04503f  k8s.gcr.io/pause:3.2                             6 minutes ago  Up 5 minutes ago                   d8b023fc4870-infra

A different COMMAND is being run for both.

Output of podman version:

podman version 2.2.1

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.18.0
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.22, commit: '
  cpus: 8
  distribution:
    distribution: ubuntu
    version: "20.04"
  eventLogger: journald
  hostname: 49c5410a9f23
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.4.0-52-generic
  linkmode: dynamic
  memFree: 552169472
  memTotal: 16423964672
  ociRuntime:
    name: runc
    package: 'cri-o-runc: /usr/lib/cri-o-runc/sbin/runc'
    path: /usr/lib/cri-o-runc/sbin/runc
    version: 'runc version spec: 1.0.2-dev'
  os: linux
  remoteSocket:
    path: /run/podman/podman.sock
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 1555668992
  swapTotal: 2147479552
  uptime: 1567h 13m 10.03s (Approximately 65.29 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 3
    paused: 0
    running: 3
    stopped: 0
  graphDriverName: vfs
  graphOptions: {}
  graphRoot: /var/lib/containers/storage
  graphStatus: {}
  imageStore:
    number: 2
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 2.1.0
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.15.2
  OsArch: linux/amd64
  Version: 2.2.1

Package info (e.g. output of rpm -q podman or apt list podman):

Listing... Done
podman/unknown,now 2.2.1~4 amd64 [installed]
podman/unknown 2.2.1~4 arm64
podman/unknown 2.2.1~4 armhf
podman/unknown 2.2.1~4 s390x

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes (latest version from the Kubic project)

Additional environment details (AWS, VirtualBox, physical, etc.):

Tested on a work computer (which uses rootless Podman) and also tested inside a privileged Docker container I setup (which is the above example).

[kiancross]

Ah looks like a duplicate of #8803 and fixed in #8807.