A library pod runs an app container and a logging sidecar. kubectl logs without a container name fails with an ambiguous-container error. What must the administrator do?
Select an answer to reveal the explanation.
Short Explanation
Two containers, one pod—kubectl won't guess which diary you want. Pass -c and name the app or the sidecar explicitly.
Full Explanation
In multi-container pods kubectl requires an explicit container selection via -c/--container when more than one container exists. Deleting sidecars, enabling hostPID, or inventing Service annotations are not the supported way to choose a log stream. Naming the container scopes logs correctly.