You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A single container pod's logs seems to work fine, but it looks like you might need to add a deeper hierarchy for containers. (the equiv. of kubectl logs podname -c containername).
But so far very fun work!
The text was updated successfully, but these errors were encountered:
I see the same problem. Need to pass kubectl the -c flag in some cases:
$ cat ~/k8s/kube-system/pod/kube-dns-v11-19scr/logs
$
$ kubectl --namespace=kube-system logs kube-dns-v11-19scrError from server: a container name must be specified for pod kube-dns-v11-19scr, choose one of: [etcd kube2sky skydns healthz]
$ kubectl --namespace=kube-system logs -c etcd kube-dns-v11-19scr2016-06-29 00:29:03.644732 I | etcdserver: start to snapshot (applied: 4810481, lastsnap: 4800480)2016-06-29 00:29:03.705105 I | etcdserver: saved snapshot at index 48104812016-06-29 00:29:03.705411 I | etcdserver: compacted raft log at 4805481...
Yes indeed. I like the simplicity of having a single logs file, but maybe we could add extra folders or files when there is more than one container in the pod.
A single container pod's logs seems to work fine, but it looks like you might need to add a deeper hierarchy for containers. (the equiv. of kubectl logs podname -c containername).
But so far very fun work!
The text was updated successfully, but these errors were encountered: