Which command executes a new command inside a running pod or container using OpenShift style syntax?

Which command executes a new command inside a running pod or container using OpenShift style syntax?

• A. oc exec [options] pod [-c container] -- command [arguments]
• B. sudo podman exec [options] container command [arguments]
• C. oc logs <podName>
• D. sudo podman run [options] container command

Answer: (A)

Running a new command inside a running pod or container in OpenShift is done with the OpenShift client’s exec command. You target the pod, optionally specify the container inside that pod with -c if there are multiple containers, and then use -- to separate the exec options from the command you want to run inside the container. This exact structure—oc exec [options] pod [-c container] -- command [arguments]—is designed for executing a fresh command inside an existing pod. Other options don’t fit OpenShift-style command execution inside a running pod: using Podman commands targets standalone containers rather than Kubernetes pods, oc logs retrieves logs rather than executing a command, and podman run starts a new container rather than executing inside an existing one.

Running a new command inside a running pod or container in OpenShift is done with the OpenShift client’s exec command. You target the pod, optionally specify the container inside that pod with -c if there are multiple containers, and then use -- to separate the exec options from the command you want to run inside the container. This exact structure—oc exec [options] pod [-c container] -- command [arguments]—is designed for executing a fresh command inside an existing pod.

Other options don’t fit OpenShift-style command execution inside a running pod: using Podman commands targets standalone containers rather than Kubernetes pods, oc logs retrieves logs rather than executing a command, and podman run starts a new container rather than executing inside an existing one.