Two Minor Issues When Using Docker to Deploy TiDB Dashboard to Access Non-K8s Cluster

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 使用docker部署tidb-dashboard访问非k8s集群的两个小问题

| username: dba-kit

【TiDB Usage Environment】Poc
【TiDB Version】v6.5.0
Currently, the K8s version already supports independent deployment of tidb-dashboard, but TiUP does not yet support standalone deployment. It appears that the image used is pingcap/tidb-dashboard:v6.5.0. After attempting to deploy it on a local physical machine, I found that 90% of the functions are usable. The only issues discovered so far are:

  1. When running, you need to add --privileged otherwise it will report an error runtime/cgo: pthread_create failed: Operation not permitted, causing the container to fail to start. (This should be avoidable through other means)

  2. No data can be retrieved in the traffic visualization tab (this is likely because the interface call was missed after independent deployment, and it did not fetch from pd)

    image
    image1295×502 23.9 KB

PS: Desperately hoping TiUP will support independent deployment of tidb-dashboard…

2
| username: liuis | Original post link

–privileged means having root privileges, right?

3
| username: dba-kit | Original post link

Yes, the risk is relatively high.

4
| username: dba-kit | Original post link

Uh, after independent deployment, the PD memory keeps increasing. After shutting down the independently deployed docker, the memory stabilizes.

5
| username: liuis | Original post link

It should be fine. Sometimes it is indeed necessary to set this to true.

6
| username: dba-kit | Original post link

During the startup period, there are many warnings on PD:
[2023/03/17 11:24:11.205 +08:00] [ERROR] [middleware.go:164] ["write failed"] [error="[PD:http:ErrWriteHTTPBody]write tcp <pd-ip>:2379-><dashboard-ip>:49092: write: connection reset by peer: write tcp <pd-ip>:2379-><dashboard-ip>:49092: write: connection reset by peer"]

7
| username: tidb菜鸟一只 | Original post link

Hasn’t version 6.5 already supported splitting the dashboard separately?