Conformance test fails if Docker is started with --log-driver=journald option.
vadbluedata opened this issue · comments
The [sig-cli] test Kubectl logs should be able to retrieve and filter logs fails when Docker is started with --log-driver=journald option. The --limit-bytes option of the kubectl logs command is ignored, and all the pod's log is returned instead of just the expected number of bytes, which causes the test to fail. Everything works ok if Docker is started with --log-driver=json-file option. (This is on CentOs 3.10.0-1062.1.2.el7.x86_64 )
@dankohn
I've observed the same problem in our test cluster.
[EDIT]
It looks like the "legacy" log implementation for docker doesn't consider length limits: https://github.com/kubernetes/kubernetes/blob/29232e3edc4202bb5e34c8c107bae4e8250cd883/pkg/kubelet/dockershim/docker_legacy_service.go#L54