# Why does etcd fail with Debian/bullseye kernel?

**URL:** <https://discuss.kubernetes.io/t/why-does-etcd-fail-with-debian-bullseye-kernel/19696>\
**Category:** General Discussions\
**Created:** [April 18, 2022, 10:26pm UTC](https://discuss.kubernetes.io/t/why-does-etcd-fail-with-debian-bullseye-kernel/19696 "2022-04-18T22:26:42Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Pravesh\_Koirala](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/pravesh_koirala/32/10143_2.png) [@Pravesh\_Koirala](https://discuss.kubernetes.io/u/Pravesh_Koirala)\
**Post date:** [May 23, 2022, 7:51pm UTC](https://discuss.kubernetes.io/t/why-does-etcd-fail-with-debian-bullseye-kernel/19696/6 "2022-05-23T19:51:28Z")

</div>

What helped me was to add `systemd.unified_cgroup_hierarchy=0` to my GRUB\_CMDLINE\_LINUX\_DEFAULT in the grub file (/etc/default/grub for Debian). After this, run `update-grub`.

I think this happened because the newer kernel is using cgroups v2 by default whereas the CRI I had (containerd I guess older version?) did not support it. Anyways, once I did that and rebooted my system it worked! Hope this helps someone (or me in the future).

---

_[View the full topic](https://discuss.kubernetes.io/t/why-does-etcd-fail-with-debian-bullseye-kernel/19696)._