# Filebeat not starting as Daemonset

**URL:** <https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904>\
**Category:** Beats\
**Created:** [May 7, 2018, 8:48pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904 "2018-05-07T20:48:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Victor\_Covalski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/victor_covalski/32/30899_2.png) [@Victor\_Covalski](https://discuss.elastic.co/u/Victor_Covalski)\
**Post date:** [May 7, 2018, 8:48pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/1 "2018-05-07T20:48:15Z")

</div>

Hi,

I'm trying to deploy Filebeat to collect logs from my Kubelets using the provided [example](https://www.elastic.co/guide/en/beats/filebeat/6.3/running-on-kubernetes.html).

Although, my filebeat container is not starting and I'm getting the following error messages

```
May 7 15:26:22 xxx kubelet: E0507 15:26:22.781732 644 pod_workers.go:186] Error syncing pod dbd96cee-5223-11e8-ad37-000c29ea6766 ("filebeat-xwfxr_kube-system(dbd96cee-5223-11e8-ad37-000c29ea6766)"), skipping: failed to "StartContainer" for "filebeat" with RunContainerError: "failed to start container \"2def5e6ae0969b060661c23ffc0542413a738d991b890f7462c50601b2467736\": Error response from daemon: linux mounts: Path /var/lib/docker/containers is mounted on /var/lib/docker/containers but it is not a shared or slave mount."
May 7 15:26:33 xxx kubelet: E0507 15:26:33.658283 644 pod_workers.go:186] Error syncing pod dbd96cee-5223-11e8-ad37-000c29ea6766 ("filebeat-xwfxr_kube-system(dbd96cee-5223-11e8-ad37-000c29ea6766)"), skipping: failed to "StartContainer" for "filebeat" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=filebeat pod=filebeat-xwfxr_kube-system(dbd96cee-5223-11e8-ad37-000c29ea6766)" ´

```

I've tried setting the MountFlags option to shared, although it didn't work.

I'm using the following versions of Kubernetes and Docker on CentOS 7

```
docker --version
Docker version 1.13.1, build 774336d/1.13.1

kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:14:26Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

```

I think I'm missing an important point or configuration here since I couldn't find any related issues on the internet.

Any help will be greatly appreciated :).

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [May 8, 2018, 8:31pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/2 "2018-05-08T20:31:56Z")

</div>

@Victor_Covalski I think you are running into an issue with bind propagation, I would check the [official docker doc](https://docs.docker.com/storage/bind-mounts/#configure-bind-propagation) if that fixes your issues we might want to update our documentation.

---

<div class="post-metadata">

**Author:** ![Victor\_Covalski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/victor_covalski/32/30899_2.png) [@Victor\_Covalski](https://discuss.elastic.co/u/Victor_Covalski)\
**Post date:** [May 9, 2018, 2:18pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/4 "2018-05-09T14:18:20Z")

</div>

Thanks @pierhugues.

Update:

After reading through the documentation I decided to confirm if my MountFlags option was being considered by Docker.

So I ran

```
findmnt -o TARGET,PROPAGATION /var/lib/docker/containers
TARGET PROPAGATION
/var/lib/docker/containers shared

```

I'm still running into the same issue. My Filebeat container image is version 6.2.4

---

<div class="post-metadata">

**Author:** ![Victor\_Covalski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/victor_covalski/32/30899_2.png) [@Victor\_Covalski](https://discuss.elastic.co/u/Victor_Covalski)\
**Post date:** [May 9, 2018, 4:41pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/5 "2018-05-09T16:41:51Z")

</div>

Update;

It seems it is a recently found bug in CentOS 7. My kernel version matches the one in the bug report found [here](https://bugs.centos.org/view.php?id=14455)

I think this thread can be closed now since it is not related to Beats.

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [May 9, 2018, 7:23pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/6 "2018-05-09T19:23:20Z")

</div>

thanks for updating it. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 6, 2018, 9:24pm UTC](https://discuss.elastic.co/t/filebeat-not-starting-as-daemonset/130904/7 "2018-06-06T21:24:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.