<p>I'm trying to get logs from my pod, but it doesn't work for some reason though <code>kubectl describe pod</code> works well, <code>docker logs</code> works well. I have Kubernetes 1.2.3 Debian 8 x64 installed manually on a single node</p>

<pre><code>  $ kubectl logs -f web-backend-alzc1 --namespace=my-namespace --v=6
  round_trippers.go:286] GET http://localhost:8080/api 200 OK in 0 milliseconds
  round_trippers.go:286] GET http://localhost:8080/apis 200 OK in 0 milliseconds
  round_trippers.go:286] GET http://localhost:8080/api/v1/namespaces/my-namespace/pods/web-backend-alzc1 200 OK in 1 milliseconds
  round_trippers.go:286] GET http://localhost:8080/api 200 OK in 0 milliseconds
  round_trippers.go:286] GET http://localhost:8080/apis 200 OK in 0 milliseconds
  round_trippers.go:286] GET http://localhost:8080/api/v1/namespaces/my-namespace/pods/web-backend-alzc1/log?follow=true 404 Not Found in 1 milliseconds
  helpers.go:172] server response object: [{
    "metadata": {},
    "status": "Failure",
    "message": "the server could not find the requested resource ( pods/log web-backend-alzc1)",
    "reason": "NotFound",
    "details": {
      "name": "web-backend-alzc1",
      "kind": "pods/log"
    },
    "code": 404
  }]
  helpers.go:107] Error from server: the server could not find the requested resource ( pods/log web-backend-alzc1)
</code></pre>

<p>Is there something I should describe in RC scheme to enable logs for this pod?</p>

<p>I tried to recreate RC and look at journalctl, I see these messages:</p>

<pre><code>  hyperkube[443]: I0510 12:14:13.754922     443 hairpin.go:51] Unable to find pair interface, setting up all interfaces: exec: "ethtool": executable file not found in $PATH
  hyperkube[443]: I0510 12:14:13.756866     443 provider.go:91] Refreshing cache for provider: *credentialprovider.defaultDockerConfigProvider
  hyperkube[435]: W0510 12:14:38.835863     435 request.go:344] Field selector: v1 - serviceaccounts - metadata.name - default: need to check if this is versioned correctly.
</code></pre>

<p>This is caused by the <code>--enable-debugging-handlers</code> flag being set to false, which prevents the kubelet from attaching to containers and fetching the logs. Restarting the kubelet without this flag (it defaults to <code>true</code>) should fix it.</p>
