<p>Yes, your assumption is correct.</p>
<p>The entries for <code>/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock</code> represent different threads or child processes of the Docker daemon. Even though the ClickHouse server is running inside a container, its processes appear as separate entries because containers run as isolated processes on the host kernel.</p>

CC BY-SA 4.0
2024-10-17T08:37:06.020Z
2024-10-17T08:37:06.020Z
hakim00
<p>I look at this screenshot:</p>
<p><a href="https://i.sstatic.net/0EkzPRCY.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/0EkzPRCY.png" alt="enter image description here" /></a></p>
<p>Am I correct to assume that the CPU consumption that is showed by <code>/usr/bin/dockerd</code> is applicable to the docker daemon itself, not the processes that run inside the containers managed by the docker? For example, the <code>/usr/bin/clickhouse-server</code> process runs inside the container, but it's shown as a separate entry in the table.</p>

<docker>
Is docker daemon process shown in htop represents the daemon itself
Max Koretskyi
# Is docker daemon process shown in htop represents the daemon itself

(Asked by: username_0 on 2024-10-15)

I look at this screenshot:

[![enter image description here](https://i.sstatic.net/0EkzPRCY.png)](https://i.sstatic.net/0EkzPRCY.png)

Am I correct to assume that the CPU consumption that is showed by `/usr/bin/dockerd` is applicable to the docker daemon itself, not the processes that run inside the containers managed by the docker? For example, the `/usr/bin/clickhouse-server` process runs inside the container, but it's shown as a separate entry in the table.

**Tags:** docker


---

## 1 answers

### Answer by username_1 on 2024-10-17. Score: 1 | Accepted answer

Yes, your assumption is correct.

The entries for `/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock` represent different threads or child processes of the Docker daemon. Even though the ClickHouse server is running inside a container, its processes appear as separate entries because containers run as isolated processes on the host kernel.


---

