How can you see logs of a particular container from a multi-container pod?

How can you see logs of a particular container from a multi-container pod?

• A. kubectl logs <pod_name> -c <container_name>
• B. kubectl logs -f <pod_name> --container <container_name>
• C. kubectl logs <container_name> -p <pod_name>
• D. kubectl describe pod <pod_name> -c <container_name>

Answer: (A)

To see logs for a specific container inside a pod that runs more than one container, you must tell kubectl which container to show. When a pod has multiple containers, the logs command requires the container to be specified with the -c (or --container) flag. So you run the pod name first, then specify the container you’re interested in, and you’ll get only that container’s logs. For example: kubectl logs <pod_name> -c <container_name>. If you want to continuously stream the logs as they’re written, you can add -f to follow. If you want logs from the previous instance of the container (before it restarted), you can add -p. The other options won’t show the logs for the chosen container: describing the pod doesn’t show the container logs, and placing the container name in the position of the pod name isn’t valid syntax.

To see logs for a specific container inside a pod that runs more than one container, you must tell kubectl which container to show. When a pod has multiple containers, the logs command requires the container to be specified with the -c (or --container) flag. So you run the pod name first, then specify the container you’re interested in, and you’ll get only that container’s logs. For example: kubectl logs -c .

If you want to continuously stream the logs as they’re written, you can add -f to follow. If you want logs from the previous instance of the container (before it restarted), you can add -p. The other options won’t show the logs for the chosen container: describing the pod doesn’t show the container logs, and placing the container name in the position of the pod name isn’t valid syntax.