Which command sends a SIGKILL to a container named my-httpd-container?

Which command sends a SIGKILL to a container named my-httpd-container?

• A. sudo podman kill -s SIGKILL my-httpd-container
• B. sudo podman kill my-httpd-container
• C. sudo podman stop -s SIGKILL my-httpd-container
• D. sudo podman rm -f my-httpd-container

Answer: (A)

You’re testing how to forcibly stop a container by sending a specific signal. The appropriate command uses the kill action with an explicit signal. By specifying -s SIGKILL, you instruct Podman to send the SIGKILL signal to the container, guaranteeing immediate termination of the container’s main process named my-httpd-container. This direct, explicit signal ensures there’s no graceful shutdown delay or fallback behavior to a different signal. Using the same kill command without designating a signal relies on a default signal, which isn’t as clear or portable across environments. The stop command is meant for graceful shutdown, sending SIGTERM first and then SIGKILL after a timeout, so it isn’t an immediate kill. Removing the container with a force option deletes the container itself rather than just stopping the process inside.

You’re testing how to forcibly stop a container by sending a specific signal. The appropriate command uses the kill action with an explicit signal. By specifying -s SIGKILL, you instruct Podman to send the SIGKILL signal to the container, guaranteeing immediate termination of the container’s main process named my-httpd-container. This direct, explicit signal ensures there’s no graceful shutdown delay or fallback behavior to a different signal.

Using the same kill command without designating a signal relies on a default signal, which isn’t as clear or portable across environments. The stop command is meant for graceful shutdown, sending SIGTERM first and then SIGKILL after a timeout, so it isn’t an immediate kill. Removing the container with a force option deletes the container itself rather than just stopping the process inside.