# GKE cos\_containerd node make filebeat unable to sending logs out **URL:** \ **Category:** Beats\ **Tags:** docker, filebeat\ **Created:** [August 31, 2021, 8:33pm UTC](https://discuss.elastic.co/t/gke-cos-containerd-node-make-filebeat-unable-to-sending-logs-out/282961 "2021-08-31T20:33:58Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vincent\_Ngai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincent_ngai/32/43594_2.png) [@Vincent\_Ngai](https://discuss.elastic.co/u/Vincent_Ngai)\ **Post date:** [August 31, 2021, 8:33pm UTC](https://discuss.elastic.co/t/gke-cos-containerd-node-make-filebeat-unable-to-sending-logs-out/282961/1 "2021-08-31T20:33:58Z")
Hi All We are using GKE , however after 1.19 version gke side will default select **cos\_containerd** as their new node image type( for remove the docker stuff) We afraid the docker version node will remove in future time However when we move the node from **docker** to **cos\_containerd** filebeat are unable to sending logging to logstash/elasticseach (without modify any one of them config) **[Containerd node images  |  Kubernetes Engine Documentation](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd)** suspect it is becox the docker engine remove form the node and then filebeat are monut **/var/lib/docker/containers** for log drain Do you guys encount this issue ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 28, 2021, 10:34pm UTC](https://discuss.elastic.co/t/gke-cos-containerd-node-make-filebeat-unable-to-sending-logs-out/282961/2 "2021-09-28T22:34:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.