在GKE /容器优化的操作系统上logging日志logging会破坏kubectl日志

很简单，我们的集群将日志驱动程序设置为json-file 。 我们希望使用journald驱动程序喂养成功。 更改日志logging驱动程序打破了kubectl logs因为它仍然在寻找json文件。 Docker logs其中的一个节点工作得很好。 有任何想法吗？

OS信息：

 CHROMEOS_AUSERVER=https://tools.google.com/service/update2 CHROMEOS_BOARD_APPID={76E245CF-C0D0-444D-BA50-36739C18EB00} CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1} CHROMEOS_DEVSERVER= CHROMEOS_RELEASE_APPID={76E245CF-C0D0-444D-BA50-36739C18EB00} CHROMEOS_RELEASE_BOARD=lakitu-signed-mpkeys CHROMEOS_RELEASE_BRANCH_NUMBER=84 CHROMEOS_RELEASE_BUILDER_PATH=lakitu-release/R60-9592.84.0 CHROMEOS_RELEASE_BUILD_NUMBER=9592 CHROMEOS_RELEASE_BUILD_TYPE=Official Build CHROMEOS_RELEASE_CHROME_MILESTONE=60 CHROMEOS_RELEASE_DESCRIPTION=9592.84.0 (Official Build) stable-channel lakitu CHROMEOS_RELEASE_NAME=Chrome OS CHROMEOS_RELEASE_PATCH_NUMBER=0 CHROMEOS_RELEASE_TRACK=stable-channel CHROMEOS_RELEASE_VERSION=9592.84.0 DEVICETYPE=OTHER GOOGLE_RELEASE=9592.84.0 HWID_OVERRIDE=LAKITU DEFAULT BUILD_ID=9592.84.0 NAME="Container-Optimized OS" KERNEL_COMMIT_ID=30321742b4e00c2250c21bb15f64cb23fa443c74 GOOGLE_CRASH_ID=Lakitu VERSION_ID=60 BUG_REPORT_URL=https://crbug.com/new PRETTY_NAME="Container-Optimized OS from Google" VERSION=60 GOOGLE_METRICS_PRODUCT_ID=26 HOME_URL="https://cloud.google.com/compute/docs/containers/vm-image/" ID=cos 

Docker版本：

Docker version 1.13.1, build 092cba3

Kubectl版本：

 Client Version: version.Info{Major:"1", Minor:"7",GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad",GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc",Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"7+", GitVersion:"v1.7.6-gke.1", GitCommit:"407dbfe965f3de06b332cc22d2eb1ca07fb4d3fb", GitTreeState:"clean", BuildDate:"2017-09-27T21:21:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}