# Netdata 1.35.1 with Containerd runtime not resolving pod names

**URL:** <https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086>\
**Category:** Help\
**Created:** [July 6, 2022, 2:17pm UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086 "2022-07-06T14:17:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![data-smith](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@data-smith](https://community.netdata.cloud/u/data-smith)\
**Post date:** [July 6, 2022, 2:17pm UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086/1 "2022-07-06T14:17:25Z")

</div>

I’m running the latest Netdata in k8s with containerd runtime with cgroups enabled. The pod names aren’t resolving. All the names look like k8s system-slice containerd-service kubepods-best-effort pod- cri-containerd   
I installed using vanilla helm chart.

Edit: I just discovered that it works with a node that has containerd 1.5.2 runtime but not with containers with containerd 1.4.6

Any advice on how to resolve?

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [July 6, 2022, 3:10pm UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086/2 "2022-07-06T15:10:21Z")

</div>

Hi. Let’s check the following for both containerd 1.5.2 and 1.4.6

```nohighlight
kubectl -n <NAMESPACE> exec -it <ND_CHILD_POD_NAME> -c netdata -- bash
apk add tree
# and share the output of this command
tree -d /host/sys/fs/cgroup

```

---

<div class="post-metadata">

**Author:** ![data-smith](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@data-smith](https://community.netdata.cloud/u/data-smith)\
**Post date:** [July 6, 2022, 10:03pm UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086/3 "2022-07-06T22:03:44Z")

</div>

I’m on a closed network so I can’t move anything on my network to the internet. But when I hop onto each one - the 1.5.2 and the 1.4.6 I see they both have those directories available.  
Also, 1.33 works but 1.35 doesn’t. The workaround for now is just use 1.33 on containerd 1.4.6 nodes.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [July 7, 2022, 7:44am UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086/4 "2022-07-07T07:44:51Z")

</div>

I can’t really help if you don’t share `tree -d /host/sys/fs/cgroup` (from inside the Netdata container) or `tree -d sys/fs/cgroup` (from host).

We did some [fixes regarding name resolution recently](https://github.com/netdata/netdata/issues/13251), but they haven’t been merged yet. I built a docker image that contains the changes, you can try it - `ilyam8/netdata-test-for-github`. Let’s fee if it fixes the problem.

---

<div class="post-metadata">

**Author:** ![data-smith](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@data-smith](https://community.netdata.cloud/u/data-smith)\
**Post date:** [July 7, 2022, 11:10am UTC](https://community.netdata.cloud/t/netdata-1-35-1-with-containerd-runtime-not-resolving-pod-names/3086/5 "2022-07-07T11:10:42Z")

</div>

> [@ilyam8](#):
>
> `ilyam8/netdata-test-for-github`

I appreciate your input but i have constraints on what I can do in the cluster and I can’t pull data off of it and I can’t run unapproved containers. For now i’ll just run 1.33 for runtime env containerd 1.4.6 and hope a) my cluster admins upgrade containerd to 1.5.2+ or b) netdata 1.36+ has a fix.