Which command creates a new process inside a running container using Podman or OpenShift tooling?

Which command creates a new process inside a running container using Podman or OpenShift tooling?

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

Answer: (B)

When you want to run something inside a container that’s already running, you’re starting a new process inside that container. In OpenShift, the standard way to do this is with an exec operation on the pod using the oc tool. The syntax oc exec [options] POD [-c CONTAINER] -- command [arguments] lets you specify which pod to target and, if needed, which container inside that pod, and the -- separates the tool’s options from the command you want to run inside the container. This approach creates a new process inside the existing container rather than starting a new container or just starting the container itself. While Podman also supports running commands inside a running container with its own exec, the OpenShift tooling here is oc exec, which is why it’s the correct match for this scenario.

When you want to run something inside a container that’s already running, you’re starting a new process inside that container. In OpenShift, the standard way to do this is with an exec operation on the pod using the oc tool. The syntax oc exec [options] POD [-c CONTAINER] -- command [arguments] lets you specify which pod to target and, if needed, which container inside that pod, and the -- separates the tool’s options from the command you want to run inside the container. This approach creates a new process inside the existing container rather than starting a new container or just starting the container itself. While Podman also supports running commands inside a running container with its own exec, the OpenShift tooling here is oc exec, which is why it’s the correct match for this scenario.